Page summary

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

Tested 2020-12-21 10:47:26 using Chrome 87.0.4280.88. 3 runs and connectivity native.  

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.2 MB
Requests98
TTFB [median]105 ms
Fully Loaded [median]2.561 s
First Visual Change [median]434 ms
First Contentful Paint (FCP) [median]432 ms
Largest Contentful Paint (LCP) [median]432 ms
Cumulative Layout Shift (CLS) [median]0.00
Total Blocking Time [median]601 ms
Max Potential FID [median]225 ms
CPU long tasks [median]15
CPU longest task duration233 ms
Speed Index [median]543 ms
Visual Complete 85% [median]568 ms
Visual Complete 99% [median]1.966 s
Last Visual Change [median]2.102 s
Screenshot of run 2

Timings Summary

Metricminmedianmeanmax
Visual Metrics
SpeedIndex539 ms543 ms555 ms583 ms
FirstVisualChange433 ms434 ms445 ms467 ms
LastVisualChange2.100 s2.102 s2.145 s2.233 s
VisualReadiness1.667 s1.668 s1.700 s1.766 s
VisualComplete85533 ms568 ms567 ms600 ms
VisualComplete951.936 s1.966 s2.001 s2.100 s
VisualComplete991.936 s1.966 s2.001 s2.100 s
RUM Metrics
TTFB102 ms105 ms107 ms115 ms
LCP415 ms432 ms439 ms469 ms
FCP415 ms432 ms439 ms469 ms
firstPaint415 ms432 ms439 ms469 ms
loadEventEnd2.085 s2.113 s2.145 s2.237 s
CLS0000
User Timing
mwStartup450 ms526 ms533 ms623 ms
CPU
Total Blocking Time526 ms601 ms592 ms648 ms
Max Potential FID223 ms225 ms227 ms233 ms
CPU long tasks 15151516
Download videoDownload timelineDownload HAR
| Waterfall | | Download HAR | 

Waterfall

Run 2 SpeedIndex median

Download HAR
| Video | Download | 

Video

Download video
| Filmstrip | 

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s
0.3 sCPU Long Task duration 151 ms
0.5 sFirst Contentful Paint 415 msLCP <P> 415 msFirst Visual Change 434 msmwStartup 450 msCPU Long Task duration 61 ms
0.6 sVisual Complete 85% 568 ms
0.7 sCPU Long Task duration 104 ms
0.9 sCPU Long Task duration 83 ms
1 sCPU Long Task duration 67 msCPU Long Task duration 52 ms
1.1 sCPU Long Task duration 56 ms
1.2 sCPU Long Task duration 55 ms
1.3 sCPU Long Task duration 120 ms
1.4 sCPU Long Task duration 57 ms
1.5 sCPU Long Task duration 62 msCPU Long Task duration 66 ms
1.6 sCPU Long Task duration 100 ms
2 sDOM Content Loaded Time 1.924 sVisual Complete 95% 1.936 sVisual Complete 99% 1.936 sCPU Long Task duration 124 ms
2.1 sPage Load Time 2.083 sCPU Long Task duration 225 ms
2.2 sLast Visual Change 2.102 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 15 CPU long tasks with the total of 1386 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
  • self
  • self
  • self
  • unknown
  • self
  • unknown
  • unknown
  • unknown
  • unknown
  • unknown
  • unknown
  • self
  • self
Avoid extra requests by setting cache headers (cacheHeaders)The page has 78 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 693.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 703.5 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 231.2 kB and the uncompressed size is 807.9 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 (85)

TitleAdviceScore
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 2 responses that sets a p3p header. There are 10 responses that sets both a max-age and expires header. There are 98 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 (88)

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.36.0-wmf.22
Width1350
Height38795
DOM elements17594
Avg DOM depth14
Max DOM depth28
Iframes0
Script tags6
Local storage591.2 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 Change434 ms
Speed Index543 ms
Visual Complete 85%568 ms
Visual Complete 95%1.936 s
Visual Complete 99%1.936 s
Last Visual Change2.102 s
Visual Readiness1.668 s

Browser Metrics

Navigation Timing
backEndTime105 ms
domContentLoadedTime1.924 s
domInteractiveTime1.923 s
domainLookupTime0 ms
frontEndTime740 ms
pageDownloadTime1.239 s
pageLoadTime2.083 s
redirectionTime0 ms
serverConnectionTime45 ms
serverResponseTime1.280 s
Google Web Vitals
Largest Contentful Paint (LCP)415 ms
Cumulative Layout Shift (CLS)0.00
Total Blocking Time (TBT)601 ms
Extra timings
First Contentful Paint (FCP)415 ms
First Paint415 ms
Largest Contentful Paint (LCP)415 ms
Load Event End2.085 s
Fully loaded2.522 s
User Timing marks
mwStartup450 ms

Largest Contentful Paint

Read more about Largest Contentful Paint.

Tag Render timeLoad timeSize
P 415 ms 0 ms 157.9 KB

Detected Cumulative Layout Shift

No layout shift detected.

Server timings

namedurationdescription
cache0hit-front

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
Documents12
Frames12
JSEventListeners1996
LayoutObjects25979
MediaKeySessions0
MediaKeys0
Nodes36386
Resources92
ContextLifecycleStateObservers26
V8PerContextDatas1
WorkerGlobalScopes0
UACSSResources0
RTCPeerConnections0
ResourceFetchers12
AdSubframes0
DetachedScriptStates0
ArrayBufferContents0
LayoutCount22
RecalcStyleCount24
LayoutDuration551
RecalcStyleDuration414
DevToolsCommandDuration10
ScriptDuration500
V8CompileDuration6
TaskDuration2562
TaskOtherDuration1081
ThreadTime2
ProcessTime3
JSHeapUsedSize4991764
JSHeapTotalSize6168576
FirstMeaningfulPaint415
| 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 requests98
Total domains3
Total transfer size1.2 MB
Total content size2.9 MB
Responses missing compression9
Number of cookies1
Third party cookies0
Requests per response code
20098

Largest assets on the page (by transfer size)

URLTypeTransfer SizeContent Size
https://en.wikipedia...wiki/Barack_Obamahtml264.3 KB1.4 MB
https://en.wikipedia...ia.org/w/load.phpjavascript163.0 KB571.2 KB
https://upload.wikim...resident_-_v1.pngimage26.4 KB26.2 KB
https://en.wikipedia...ia.org/w/load.phpjavascript21.3 KB65.0 KB
https://upload.wikim...n_Oval_Office.jpgimage20.5 KB20.3 KB
https://en.wikipedia...ia.org/w/load.phpjavascript18.6 KB72.1 KB
https://upload.wikim...y%2C_2004.svg.pngimage18.6 KB18.5 KB
https://upload.wikim..._Barack_Obama.jpgimage18.3 KB18.2 KB
https://upload.wikim...%2C_1963-2015.pngimage18.3 KB18.0 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...hing_football.jpgimage16.8 KB16.6 KB
https://upload.wikim...rora_shooting.jpgimage16.5 KB16.3 KB
https://upload.wikim...secretaries_2.jpgimage16.5 KB16.3 KB
https://upload.wikim...ign_trips.svg.pngimage16.3 KB16.1 KB
https://upload.wikim...ama-venice-la.jpgimage16.0 KB15.9 KB
https://upload.wikim...C3%BAl_Castro.jpgimage15.8 KB15.7 KB
https://upload.wikim..._and_children.jpgimage15.6 KB15.3 KB
https://upload.wikim...Office_-_crop.jpgimage15.6 KB15.4 KB
https://en.wikipedia...ia.org/w/load.phpjavascript15.3 KB55.4 KB

Requests and sizes per content type

ContentHeader SizeTransfer SizeContent SizeRequests
html0 b264.3 KB1.4 MB1
css0 b14.6 KB60.7 KB2
javascript0 b225.8 KB788.9 KB6
image0 b684.9 KB669.8 KB78
svg0 b8.5 KB17.2 KB10
favicon0 b1.2 KB2.7 KB1
Total0 b1.2 MB2.9 MB98

Size and requests per domain

DomainHeader SizeTransfer SizeContent SizeRequests
en.wikipedia.orgN/A522.2 KB2.3 MB20
upload.wikimedia.orgN/A676.8 KB662.1 KB77
login.wikimedia.orgN/A466 B236 B1

Expires and last modified statistics

typeminmedianmax
Expires0 seconds0 seconds1 year
Last modified1 minute2 years7 years

Requests loaded after onLoad event

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript18.6 KB1
image0 b0
font0 b0
svg1.2 KB2
favicon1.2 KB1
Total21.1 KB4

Requests loaded after onContentLoad

Includes requests done after onLoad.

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript18.6 KB1
image0 b0
font0 b0
svg1.2 KB2
favicon1.2 KB1
Total21.1 KB4
| 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 601
Max Potential First Input Delay 225
Long Tasks before First Paint1151
Long Tasks before First Contentful Paint1151
Long Tasks after Load Event End2344
Total Long Tasks161502

Individual Long Tasks

namestartTimedurationcontainerIdcontainerNamecontainerSrccontainerType
unknown210151window
unknown47261window
unknown696104window
self82983window
self91367window
unknown99952window
self107556window
unknown113955window
self1214120window
unknown134957window
unknown142562window
unknown149766window
unknown1593100window
unknown1952124window
self2100225window
self2549119window

CPU time spent

Calculated using Tracium.

Categories (ms)
parseHTML128
styleLayout968
paintCompositeRender390
scriptParseCompile6
scriptEvaluation493
garbageCollection65
other545
Events (ms)
Layout552
RunTask461
UpdateLayoutTree416
V8.Execute369
UpdateLayerTree308
ParseHTML125
V8.HandleInterrupts100
Paint57
BlinkGC.VisitRoots18
BlinkGC.LazySweepInIdle15
CompositeLayers14

Time spent per request

URLCPU time (ms)
https://en.wikipedia.org/w/load.php?lang=en&modules=Spinner%2Cjquery%2Coojs%2Coojs-router%2Csite%7Cext.categoryTree%2CeventLogging%2CnavigationTiming%2Cpopups%2CwikimediaEvents%7Cext.centralNotice.bannerHistoryLogger%2CchoiceData%2Cdisplay%2CgeoIP%2CimpressionDiet%2CkvStore%2ClargeBannerLimit%2ClegacySupport%2CstartUp%7Cext.centralauth.centralautologin%7Cext.cite.ux-enhancements%7Cext.cx.eventlogging.campaigns%7Cext.tmh.OgvJsSupport%7Cext.uls.common%2Ccompactlinks%2Cinterface%2Cpreferences%2Cwebfonts%7Cjquery.client%2Ccookie%2CembedPlayer%2CloadingSpinner%2CmakeCollapsible%2CmwEmbedUtil%2CtextSelection%2CtriggerQueueCallback%7Cjquery.uls.data%7Cmediawiki.String%2CTitle%2CUri%2Capi%2Cbase%2Ccldr%2Ccookie%2Cexperiments%2CjqueryMsg%2Clanguage%2Cstorage%2Ctoc%2Cuser%2Cutil%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=g516x310
https://en.wikipedia.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector191

CPU time spent

Tool/domainTime (ms)
en.wikipedia.org500.5
| 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 b264.3 KB1.4 MB1
css0 b14.6 KB60.7 KB2
javascript0 b225.8 KB788.9 KB6
image0 b684.9 KB669.8 KB78
font0 b0 b0 b0
svg0 b8.5 KB17.2 KB10
favicon0 b1.2 KB2.7 KB1
TotalN/A1.2 MB2.9 MB98

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