Run 2 summary

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

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

All runs: 1 - 2 - 3

Back to summary
SummaryWaterfall MetricsVideoFilmstrip CoachPageXrayCPU Third partyScreenshots

Summary

MetricValue
Performance score76
Total page size324.6 KB
Requests33
TTFB247 ms
Fully Loaded1.270 s
First Visual Change617 ms
FCP600 ms
LCP600 ms
CLS0
Total Blocking Time64 ms
Max Potential FID101 ms
CPU long tasks3
Speed Index625 ms
Visual Complete 85%617 ms
Visual Complete 99%892 ms
Last Visual Change1.166 s
Screenshot
Download videoDownload timeline
| Waterfall | | Download HAR | 

Waterfall

Download HAR
| Video | Download | 

Video

Download video
| Filmstrip | 

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s
0.5 sCPU Long Task duration 104 ms
0.6 sDOM Content Loaded Time 556 msmwStartup 567 msFirst Contentful Paint 600 msLCP <P> 600 ms
0.7 sFirst Visual Change 617 msVisual Complete 85% 617 msVisual Complete 95% 617 ms
0.9 sVisual Complete 99% 892 ms
1 sCPU Long Task duration 62 ms
1.2 sCPU Long Task duration 101 msLast Visual Change 1.166 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 (76)

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 3 CPU long tasks with the total of 267 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.40
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
  • self
  • self
Avoid extra requests by setting cache headers (cacheHeaders)The page has 19 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 85.1 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 JavaScript size shouldn't be too big (javascriptSize)The total JavaScript transfer size is 200.9 kB and the uncompressed size is 717.8 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 (86)

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 9 responses that sets both a max-age and expires header. There are 33 responses that sets a server header. 56
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
TitleWikipedia, the free encyclopedia
GeneratorMediaWiki 1.36.0-wmf.22
Width1350
Height2745
DOM elements1069
Avg DOM depth11
Max DOM depth18
Iframes0
Script tags6
Local storage496.6 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 Change617 ms
Speed Index625 ms
Visual Complete 85%617 ms
Visual Complete 95%617 ms
Visual Complete 99%892 ms
Last Visual Change1.166 s
Visual Readiness549 ms

Browser Metrics

Navigation Timing
backEndTime247 ms
domContentLoadedTime556 ms
domInteractiveTime555 ms
domainLookupTime0 ms
frontEndTime967 ms
pageDownloadTime4 ms
pageLoadTime1.219 s
redirectionTime0 ms
serverConnectionTime83 ms
serverResponseTime153 ms
Google Web Vitals
Largest Contentful Paint (LCP)600 ms
Cumulative Layout Shift (CLS)0.00
Total Blocking Time (TBT)64 ms
Extra timings
First Contentful Paint (FCP)600 ms
First Paint600 ms
Largest Contentful Paint (LCP)600 ms
Load Event End1.220 s
Fully loaded1.270 s
User Timing marks
mwStartup567 ms

Largest Contentful Paint

Read more about Largest Contentful Paint.

Tag Render timeLoad timeSize
P 600 ms 0 ms 162.4 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
Documents11
Frames6
JSEventListeners46
LayoutObjects1923
MediaKeySessions0
MediaKeys0
Nodes2740
Resources34
ContextLifecycleStateObservers24
V8PerContextDatas1
WorkerGlobalScopes0
UACSSResources0
RTCPeerConnections0
ResourceFetchers11
AdSubframes0
DetachedScriptStates0
ArrayBufferContents2
LayoutCount10
RecalcStyleCount14
LayoutDuration76
RecalcStyleDuration44
DevToolsCommandDuration9
ScriptDuration335
V8CompileDuration7
TaskDuration688
TaskOtherDuration216
ThreadTime1
ProcessTime1
JSHeapUsedSize6987588
JSHeapTotalSize10866688
FirstMeaningfulPaint600
| 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 requests33
Total domains3
Total transfer size324.6 KB
Total content size929.7 KB
Responses missing compression8
Number of cookies2
Third party cookies0
Requests per response code
20033

Largest assets on the page (by transfer size)

URLTypeTransfer SizeContent Size
https://en.wikipedia...ia.org/w/load.phpjavascript133.3 KB483.2 KB
https://upload.wikim...llayer-Coster.jpgimage27.7 KB27.5 KB
https://en.wikipedia...ia.org/w/load.phpjavascript21.3 KB65.0 KB
https://en.wikipedia.org/wiki/Main_Pagehtml20.7 KB81.7 KB
https://en.wikipedia...ia.org/w/load.phpjavascript18.6 KB72.1 KB
https://en.wikipedia...ia.org/w/load.phpjavascript15.3 KB55.4 KB
https://upload.wikim...57px-Change-5.pngimage14.4 KB14.3 KB
https://en.wikipedia...ia.org/w/load.phpcss9.0 KB38.2 KB
https://en.wikipedia...-logos/enwiki.pngimage8.6 KB8.4 KB
https://en.wikipedia...ia.org/w/load.phpjavascript7.1 KB25.1 KB
https://upload.wikim...%28raccoon%29.jpgimage6.9 KB6.8 KB
https://upload.wikim...o_Orjonikidze.jpgimage6.7 KB6.1 KB
https://upload.wikim...n_Gulf-region.jpgimage5.2 KB5.1 KB
https://en.wikipedia...ia.org/w/load.phpcss4.7 KB17.1 KB
https://upload.wikim...en_A_Poil_Ras.jpgimage3.9 KB3.7 KB
https://upload.wikim...news-logo.svg.pngimage2.5 KB2.4 KB
https://upload.wikim...ediawiki-logo.pngimage2.5 KB2.3 KB
https://upload.wikim...cies-logo.svg.pngimage2.5 KB2.3 KB
https://upload.wikim...urce-logo.svg.pngimage1.7 KB1.5 KB
https://upload.wikim...ooks-logo.svg.pngimage1.6 KB1.5 KB

Requests and sizes per content type

ContentHeader SizeTransfer SizeContent SizeRequests
html0 b20.7 KB81.7 KB1
css0 b13.6 KB55.3 KB2
javascript0 b196.2 KB700.9 KB6
image0 b91.2 KB87.7 KB19
svg0 b1.7 KB1.5 KB4
favicon0 b1.2 KB2.7 KB1
Total0 b324.6 KB929.7 KB33

Size and requests per domain

DomainHeader SizeTransfer SizeContent SizeRequests
en.wikipedia.orgN/A241.5 KB850.2 KB14
upload.wikimedia.orgN/A82.6 KB79.3 KB18
login.wikimedia.orgN/A466 B236 B1

Expires and last modified statistics

typeminmedianmax
Expires0 seconds0 seconds1 year
Last modified10 seconds1 week5 years

Requests loaded after onLoad event

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript18.6 KB1
image0 b0
font0 b0
favicon1.2 KB1
Total19.9 KB2

Requests loaded after onContentLoad

Includes requests done after onLoad.

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript174.8 KB5
image17.8 KB12
font0 b0
svg671 B1
favicon1.2 KB1
Total194.5 KB19
| 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 64
Max Potential First Input Delay 101
Long Tasks before First Paint1104
Long Tasks before First Contentful Paint1104
Long Tasks after Load Event End00
Total Long Tasks3267

Individual Long Tasks

namestartTimedurationcontainerIdcontainerNamecontainerSrccontainerType
unknown445104window
self90962window
self1114101window

CPU time spent

Calculated using Tracium.

Categories (ms)
parseHTML33
styleLayout122
paintCompositeRender42
scriptParseCompile7
scriptEvaluation334
garbageCollection18
other168
Events (ms)
V8.Execute214
RunTask163
V8.HandleInterrupts100
Layout77
UpdateLayoutTree45
ParseHTML30
Paint15

Time spent per request

URLCPU time (ms)
https://en.wikipedia.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector216
https://login.wikimedia.org/wiki/Special:CentralAutoLogin/checkLoggedIn?type=script&wikiid=enwiki&proto=https101
https://en.wikipedia.org/w/load.php?lang=en&modules=ext.categoryTree%2CeventLogging%2CnavigationTiming%2Cpopups%2CwikimediaEvents%7Cext.centralNotice.bannerHistoryLogger%2CchoiceData%2Cdisplay%2CgeoIP%2CimpressionDiet%2CkvStore%2ClargeBannerLimit%2ClegacySupport%2CstartUp%7Cext.centralauth.centralautologin%7Cext.cx.eventlogging.campaigns%7Cext.uls.interface%2Cpreferences%2Cwebfonts%7Cjquery%2Coojs%2Coojs-router%2Csite%7Cjquery.client%2Ccookie%2CtextSelection%7Cmediawiki.String%2CTitle%2CUri%2Capi%2Cbase%2Ccldr%2Ccookie%2Cexperiments%2CjqueryMsg%2Clanguage%2Cstorage%2Cuser%2Cutil%7Cmediawiki.editfont.styles%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.ready%7Cmediawiki.ui.button%2Cicon%7Cmmv.bootstrap%2Chead%7Cmmv.bootstrap.autostart%7Cskins.vector.legacy.js%7Cuser.defaults&skin=vector&version=crf7461

CPU time spent

Tool/domainTime (ms)
en.wikipedia.org276.5
login.wikimedia.org100.8
| 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 b20.7 KB81.7 KB1
css0 b13.6 KB55.3 KB2
javascript0 b196.2 KB700.9 KB6
image0 b91.2 KB87.7 KB19
font0 b0 b0 b0
svg0 b1.7 KB1.5 KB4
favicon0 b1.2 KB2.7 KB1
TotalN/A324.6 KB929.7 KB33

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
| afterPageCompleteCheck.png | 

Screenshots

afterPageCompleteCheck.png

afterPageCompleteCheck.png