Page summary

https://en.wikipedia.org/wiki/Barack_Obama

Tested using Chrome 90.0.4430.85 (runtime settings).

All runs: 1 - 2 - 3

SummaryWaterfall MetricsVideoFilmstrip CoachPageXrayCPU Third party
| Summary | | Download Video | Download Timeline Log | Download HAR | 

Summary

MetricValue
Performance Score72
Total Page Transfer Size1.3 MB
Requests105
TTFB [median]159 ms
Fully Loaded [median]2.434 s
First Visual Change [median]573 ms
First Contentful Paint (FCP) [median]556 ms
Largest Contentful Paint (LCP) [median]556 ms
Cumulative Layout Shift (CLS) [median]0.04
Total Blocking Time [median]407 ms
Max Potential FID [median]193 ms
CPU long tasks [median]13
CPU longest task duration329 ms
Speed Index [median]620 ms
Visual Complete 85% [median]674 ms
Visual Complete 99% [median]1.900 s
Last Visual Change [median]2.400 s
Screenshot of run 3

Timings Summary

Metricminmedianmeanmax
Visual Metrics
SpeedIndex509 ms620 ms627 ms751 ms
FirstVisualChange467 ms573 ms583 ms710 ms
LastVisualChange2.161 s2.400 s2.352 s2.494 s
VisualReadiness1.451 s1.921 s1.768 s1.933 s
VisualComplete85533 ms674 ms682 ms839 ms
VisualComplete95533 ms674 ms682 ms839 ms
VisualComplete991.645 s1.900 s1.845 s1.989 s
RUM Metrics
TTFB130 ms159 ms181 ms253 ms
LCP454 ms556 ms576 ms717 ms
FCP454 ms556 ms576 ms717 ms
firstPaint454 ms556 ms576 ms717 ms
loadEventEnd1.995 s2.169 s2.201 s2.438 s
CLS0.04440.04440.04440.0444
User Timing
mwStartup521 ms630 ms697 ms939 ms
mwCentralNoticeBanner2.011 s2.268 s2.201 s2.326 s
CPU
Total Blocking Time364 ms407 ms409 ms457 ms
Max Potential FID103 ms193 ms167 ms205 ms
CPU long tasks 12131314
Download videoDownload timelineDownload HAR
| Waterfall | | Download HAR | 

Waterfall

Run 3 SpeedIndex median

Download HAR
| Video | Download | 

Video

Download video
| Filmstrip | 

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s
0.4 sCPU Long Task duration 123 ms
0.6 sFirst Contentful Paint 556 msLCP <P> 556 msFirst Visual Change 573 ms
0.7 smwStartup 630 msVisual Complete 85% 674 msVisual Complete 95% 674 ms
0.8 s
1 sCPU Long Task duration 51 ms
1.2 sCPU Long Task duration 65 msCPU Long Task duration 60 ms
1.3 sCPU Long Task duration 56 ms
1.4 sCPU Long Task duration 61 ms
1.5 sCPU Long Task duration 76 ms
1.6 sCPU Long Task duration 117 ms
1.7 sCPU Long Task duration 69 ms
1.9 sCPU Long Task duration 97 ms
2 sVisual Complete 99% 1.989 sDOM Content Loaded Time 1.996 s
2.1 sCPU Long Task duration 205 ms
2.4 smwCentralNoticeBanner 2.326 sCPU Long Task duration 69 ms
2.5 sLayout Shift 0.04424 2.417 sPage Load Time 2.438 sLayout Shift 0.00016 2.449 sLast Visual Change 2.494 s
| Performance advice | Best practice advice | Privacy advice | Page info | Technologies | 

Coach

The coach helps you find performance problems on your web page using web performance best practice rules. And gives you advice on privacy and best practices.

I am the coach

Coach score

Performance advice (72)

TitleAdviceScore
Inline CSS for faster first render (inlineCss)The page has both inline CSS and CSS requests even though it uses a HTTP/2-ish connection. If you have many users on slow connections, it can be better to only inline the CSS. Run your own tests and check the waterfall graph to see what happens.95
Description: In the early days of the Internet, inlining CSS was one of the ugliest things you can do. That has changed if you want your page to start rendering fast for your user. Always inline the critical CSS when you use HTTP/1 and HTTP/2 (avoid doing CSS requests that block rendering) and lazy load and cache the rest of the CSS. It is a little more complicated when using HTTP/2. Does your server support HTTP push? Then maybe that can help. Do you have a lot of users on a slow connection and are serving large chunks of HTML? Then it could be better to use the inline technique, becasue some servers always prioritize HTML content over CSS so the user needs to download the HTML first, before the CSS is downloaded.
Avoid CPU Long Tasks (longTasks)The page has 14 CPU long tasks with the total of 1269 ms. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. Use Geckoprofiler for Firefox or Chromes tracelog to debug your Long Task.0
Description: Long CPU tasks locks the thread. To the user this is commonly visible as a "locked up" page where the browser is unable to respond to user input; this is a major source of bad user experience on the web today. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using.
Offenders:
  • unknown
  • unknown
  • unknown
  • unknown
  • self
  • self
  • unknown
  • self
  • unknown
  • self
  • unknown
  • self
  • self
  • self
Avoid extra requests by setting cache headers (cacheHeaders)The page has 84 requests that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 766.5 kB the next access.0
Description: The easiest way to make your page fast is to avoid doing requests to the server. Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! Always try to set a cache time if the content doesn't change for every request.
Offenders:
Long cache headers is good (cacheHeadersLong)The page has 3 requests that have a shorter cache time than 30 days (but still a cache time).97
Description: Setting a cache header is good. Setting a long cache header (at least 30 days) is even better beacause then it will stay long in the browser cache. But what do you do if that asset change? Rename it and the browser will pick up the new version.
Offenders:
Total image size shouldn't be too big (imageSize)The page total image size is 776.1 kB. It's really big. Is the page using the right format for the images? Are they compressed as good as they can be? Make them smaller by using https://imageoptim.com/.50
Description: Avoid having too many large images on the page. The images will not affect the first paint of the page, but it will eat bandwidth for the user.
Total JavaScript size shouldn't be too big (javascriptSize)The total JavaScript transfer size is 238.1 kB and the uncompressed size is 834.6 kB. This is quite large. 0
Description: A lot of JavaScript often means you are downloading more than you need. How complex is the page and what can the user do on the page? Do you use multiple JavaScript frameworks?
Don't use private headers on static content (privateAssets)The page has 2 requests with private headers. The main page has a private header. It could be right in some cases where the user can be logged in and served specific content. But if your asset is static it should never be private. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone.90
Description: If you set private headers on content, that means that the content are specific for that user. Static content should be able to be cached and used by everyone. Avoid setting the cache header to private.
Offenders:

Best practice advice (84)

TitleAdviceScore
Cumulative Layout Shift (layoutShift)You have elements that shift. You should manually check the filmstrip or video and check if it will affect the user.96
Description: Cumulative Layout Shift measures the sum total of all individual layout shift scores for every unexpected layout shift that occurs during the entire lifespan of the page. A layout shift occurs any time a visible element changes its position from one rendered frame to the next.
Offenders:
  • H1 firstHeading
  • DIV
  • DIV mw-body-content mw-content-ltr
  • #text undefined
Meta description (metaDescription)The page is missing a meta description.0
Description: Use a page description to make the page more relevant to search engines.
Avoid Unnecessary Headers (unnecessaryHeaders)There are 3 responses that sets a p3p header. There are 10 responses that sets both a max-age and expires header. There are 105 responses that sets a server header. 0
Description: Do not send headers that you don't need. We look for p3p, cache-control and max-age, pragma, server and x-frame-options headers. Have a look at Andrew Betts - Headers for Hackers talk as a guide https://www.youtube.com/watch?v=k92ZbrY815c or read https://www.fastly.com/blog/headers-we-dont-want.
Offenders:

Privacy advice (90)

TitleAdviceScore
Use a good Content-Security-Policy header to make sure you you avoid Cross Site Scripting (XSS) attacks. (contentSecurityPolicyHeader)Set a Content-Security-Policy header to make sure you are not open for Cross Site Scripting (XSS) attacks. You can start with setting a Content-Security-Policy-Report-Only header, that will only report the violation, not stop the download.0
Description: Content Security Policy is delivered via a HTTP response header, and defines approved sources of content that the browser may load. It can be an effective countermeasure to Cross Site Scripting (XSS) attacks and is also widely supported and usually easily deployed. https://scotthelme.co.uk/content-security-policy-an-introduction/.
Offenders:
Set a referrer-policy header to make sure you do not leak user information. (referrerPolicyHeader)Set a referrer-policy header to make sure you do not leak user information.0
Description: Referrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites. https://scotthelme.co.uk/a-new-security-header-referrer-policy/.
Offenders:

Page info

Page info
TitleBarack Obama - Wikipedia
GeneratorMediaWiki 1.37.0-wmf.6
Width1350
Height40983
DOM elements18960
Avg DOM depth14
Max DOM depth29
Iframes0
Script tags6
Local storage611.5 KB
Session storage0 b
HTML vs AMPPlain good HTML page
Resource Hints
dns-prefetch
https://login.wikimedia.org/
https://meta.wikimedia.org/
preconnect
https://upload.wikimedia.org/

Technologies used to build the page.

Data collected using Wappalyzer.  Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyser find more information about technologies used.

TechnologyConfidenceCategory
MediaWiki 100  Wikis
PHP 100  Programming languages
Bootstrap 2100  UI frameworks
jQuery 100  JavaScript libraries
| Browser metrics | Visual Metrics | Largest Contentful Paint | Cumulative Layout Shift | Metrics from CDP | Server timings | 

Visual Metrics

Visual Metrics
First Visual Change573 ms
Speed Index620 ms
Visual Complete 85%674 ms
Visual Complete 95%674 ms
Visual Complete 99%1.989 s
Last Visual Change2.494 s
Visual Readiness1.921 s

Browser Metrics

Navigation Timing
backEndTime253 ms
domContentLoadedTime1.996 s
domInteractiveTime1.995 s
domainLookupTime2 ms
frontEndTime1.092 s
pageDownloadTime1.092 s
pageLoadTime2.438 s
redirectionTime0 ms
serverConnectionTime93 ms
serverResponseTime1.233 s
Google Web Vitals
First Contentful Paint (FCP)556 ms
Largest Contentful Paint (LCP)556 ms
Cumulative Layout Shift (CLS)0.04
Total Blocking Time (TBT)407 ms
Extra timings
First Contentful Paint (FCP)556 ms
First Paint556 ms
Largest Contentful Paint (LCP)556 ms
Load Event End2.438 s
Fully loaded2.503 s
User Timing marks
mwStartup630 ms
mwCentralNoticeBanner2.326 s

Largest Contentful Paint

When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.

Element typeP
Element/tag<p></p>
Render time 556 ms
Load time0 ms
Size (width*height)161472
DOM path
div#content > div#bodyContent > div#mw-content-text > div:eq(0) > p:eq(2)> div#content > div#bodyContent > div#mw-content-text > div:eq(0) > p:eq(2)>
LCP

The largest contentful paint is highlighted in the image. If no element is highlighted the element was removed before the screenshot or the LCP API couldn't find the element.

Detected Cumulative Layout Shift

0.04439 cumulative layout shift collected from the Cumulative Layout Shift API.

These HTML elements contribute most to the Cumulative Layout Shifts of the page. The higher score, the more layout shift.

ScoreHTML Element
0.04424<h1 id="firstHeading" class="firstHeading"></h1>,<div id="bodyContent"></div>,<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"></div>
body > div#content > h1#firstHeading,body > div#content > div#bodyContent,body > div#content > div#bodyContent > div#mw-content-text
0.00016
body > div#content > div#siteNotice > div#centralNotice > div:eq(0) > div:eq(1) > center > span > a > #text
Layout shift

The elements that have shifted place is highlighted in the image (that have a higher value than 0.01). If the element shifted outside of the viewport, you will not see it there. It can be hard to understand what content that has shifted, if that's the case, checkout the video or the filmstrip of the run.

Server timings

namedurationdescription
cache0hit-front
host0cp3058

Custom metrics collected through JavaScript

There are no custom configured scripts.

Extra metrics collected using scripting

There are no custom extra metrics from scripting.

CDP Performance

namevalue
AudioHandlers0
Documents13
Frames13
JSEventListeners2065
LayoutObjects27521
MediaKeySessions0
MediaKeys0
Nodes39092
Resources97
ContextLifecycleStateObservers28
V8PerContextDatas1
WorkerGlobalScopes0
UACSSResources0
RTCPeerConnections0
ResourceFetchers13
AdSubframes0
DetachedScriptStates0
ArrayBufferContents0
LayoutCount24
RecalcStyleCount26
LayoutDuration437
RecalcStyleDuration299
DevToolsCommandDuration9
ScriptDuration457
V8CompileDuration6
TaskDuration2339
TaskOtherDuration1132
ThreadTime2
ProcessTime3
JSHeapUsedSize5104136
JSHeapTotalSize6340608
FirstMeaningfulPaint556
| Summary | | Largest responses | | Requests and sizes per content type | | Size and requests per domain | | Expires and last modified statistics | | Requests loaded after onLoad event | | 

PageXray

How the page is built.

Summary
HTTP versionHTTP/2.0
Total requests105
Total domains4
Total transfer size1.3 MB
Total content size3.1 MB
Responses missing compression10
Number of cookies2
Third party cookies0
Requests per response code
200105

Largest assets on the page (by transfer size)

URLTypeTransfer SizeContent Size
https://en.wikipedia...wiki/Barack_Obamahtml280.3 KB1.5 MB
https://en.wikipedia...ia.org/w/load.phpjavascript167.9 KB591.5 KB
https://upload.wikim...resident_-_v1.pngimage28.6 KB28.4 KB
https://upload.wikim...llege2012.svg.pngimage27.5 KB27.3 KB
https://upload.wikim...llege2008.svg.pngimage27.5 KB27.3 KB
https://upload.wikim..._Barack_Obama.jpgimage22.5 KB21.8 KB
https://upload.wikim...school_record.jpgimage22.2 KB22.0 KB
https://en.wikipedia...ia.org/w/load.phpjavascript21.4 KB65.8 KB
https://upload.wikim...n_Oval_Office.jpgimage20.5 KB20.3 KB
https://en.wikipedia...ia.org/w/load.phpjavascript19.5 KB75.3 KB
https://upload.wikim...y%2C_2004.svg.pngimage18.6 KB18.5 KB
https://upload.wikim...tatistics.svg.pngimage17.3 KB17.1 KB
https://upload.wikim...eting_2009-11.jpgimage16.9 KB16.7 KB
https://upload.wikim...rora_shooting.jpgimage16.5 KB16.3 KB
https://upload.wikim...secretaries_2.jpgimage16.5 KB16.3 KB
https://upload.wikim...ama-venice-la.jpgimage16.0 KB15.9 KB
https://upload.wikim...portrait_crop.jpgimage15.8 KB15.7 KB
https://upload.wikim...C3%BAl_Castro.jpgimage15.8 KB15.7 KB
https://upload.wikim..._and_children.jpgimage15.5 KB15.3 KB
https://upload.wikim...Office_-_crop.jpgimage15.5 KB15.4 KB

Requests and sizes per content type

ContentHeader SizeTransfer SizeContent SizeRequests
html0 b280.3 KB1.5 MB1
css0 b13.8 KB59.8 KB2
javascript0 b232.6 KB815.0 KB7
image0 b754.2 KB738.3 KB82
svg0 b9.7 KB19.5 KB12
favicon0 b1.2 KB2.7 KB1
Total0 b1.3 MB3.1 MB105

Size and requests per domain

DomainHeader SizeTransfer SizeContent SizeRequests
en.wikipedia.orgN/A543.2 KB2.4 MB21
upload.wikimedia.orgN/A747.1 KB732.7 KB82
login.wikimedia.orgN/A451 B236 B1
meta.wikimedia.orgN/A944 B1.8 KB1

Expires and last modified statistics

typeminmedianmax
Expires0 seconds0 seconds1 year
Last modified42 seconds2 years8 years

Requests loaded after onLoad event

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript19.5 KB1
image2.7 KB2
font0 b0
svg1.2 KB2
favicon1.2 KB1
Total24.6 KB6

Requests loaded after onContentLoad

Includes requests done after onLoad.

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript19.5 KB1
image2.7 KB2
font0 b0
svg1.2 KB2
favicon1.2 KB1
Total24.6 KB6
| CPU Long Tasks | CPU Time Spent | CPU Time Spent Per Request | CPU Time Per Tool/Domain | 

CPU

Download the Chrome trace log and drag and drop it into Developer Tools / Performance in Chrome.

Download trace log

Long Tasks

Collected using the Long Task API. A long task is a task that take 50 milliseconds or more.

TypeQuantityTotal duration (ms)
Total Blocking Time 407
Max Potential First Input Delay 205
Long Tasks before First Paint1123
Long Tasks before First Contentful Paint1123
Long Tasks after Load Event End181
Total Long Tasks131130

Individual Long Tasks

namestartTimedurationcontainerIdcontainerNamecontainerSrccontainerType
unknown381123window
unknown99351window
self111565window
self119060window
unknown126256window
self134761window
unknown141976window
self1511117window
unknown164469window
unknown185297window
self2058205window
self235569window
self253281window

CPU time spent

Calculated using Tracium.

Categories (ms)
parseHTML120
styleLayout738
paintCompositeRender488
scriptParseCompile7
scriptEvaluation453
garbageCollection51
other496
Events (ms)
RunTask438
Layout437
UpdateLayerTree414
V8.Execute330
UpdateLayoutTree301
ParseHTML117
V8.HandleInterrupts100
Paint51
CompositeLayers18
BlinkGC.LazySweepInIdle15

Time spent per request

URLCPU time (ms)
https://en.wikipedia.org/w/load.php?lang=en&modules=ext.centralNotice.bannerHistoryLogger%2CchoiceData%2Cdisplay%2CgeoIP%2CimpressionDiet%2CkvStore%2ClargeBannerLimit%2ClegacySupport%2CstartUp%7Cext.centralauth.centralautologin%7Cext.cite.ux-enhancements%7Cext.cx.eventlogging.campaigns%7Cext.eventLogging%2CnavigationTiming%2Cpopups%2CwikimediaEvents%7Cext.growthExperiments.SuggestedEditSession%7Cext.scribunto.logs%7Cext.tmh.OgvJsSupport%7Cext.uls.common%2Ccompactlinks%2Cinterface%2Cpreferences%2Cwebfonts%7Cjquery%2Coojs%2Coojs-router%2Csite%7Cjquery.client%2Ccookie%2CembedPlayer%2CmakeCollapsible%2CmwEmbedUtil%2CtextSelection%2CtriggerQueueCallback%7Cjquery.uls.data%7Cmediawiki.String%2CTitle%2CUri%2Capi%2Cbase%2Ccldr%2Ccookie%2Cexperiments%2CjqueryMsg%2Clanguage%2Cstorage%2Ctoc%2Cuser%2Cutil%2CvisibleTimeout%7Cmediawiki.editfont.styles%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.ready%7Cmediawiki.ui.button%2Cicon%7Cmmv.bootstrap%2Chead%7Cmmv.bootstrap.autostart%7Cmw.EmbedPlayer.loader%7Cmw.MediaWikiPlayer.loader%7Cmw.MwEmbedSupport%2CPopUpMediaTransform%7Cmw.MwEmbedSupport.style%7Cmw.PopUpMediaTransform.styles%7Cmw.TMHGalleryHook.js%7Cmw.TimedText.loader%7Cskins.vector.legacy.js%7Cuser.defaults&skin=vector&version=9l6ah288
https://en.wikipedia.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector169

CPU time spent

Tool/domainTime (ms)
en.wikipedia.org456.3
| First vs third | 

Third party

Third party requests categorised by Third party web.

First party requests and sizes per content type

Calculated using (.*wikipedia.*||.*wikimedia.*) (use --firstParty to configure).

ContentHeader SizeTransfer SizeContent SizeRequests
html0 b280.3 KB1.5 MB1
css0 b13.8 KB59.8 KB2
javascript0 b232.6 KB815.0 KB7
image0 b754.2 KB738.3 KB82
font0 b0 b0 b0
svg0 b9.7 KB19.5 KB12
favicon0 b1.2 KB2.7 KB1
TotalN/A1.3 MB3.1 MB105

Third party requests and sizes per content type

ContentHeader SizeTransfer SizeContent SizeRequests
html0 b0 b0 b0
css0 b0 b0 b0
javascript0 b0 b0 b0
image0 b0 b0 b0
font0 b0 b0 b0
TotalN/AN/AN/A