Run 2 summary

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

Tested using Chrome 90.0.4430.85 (runtime settings).

All runs: 1 - 2 - 3

Back to summary
SummaryWaterfall MetricsVideoFilmstrip CoachPageXrayCPU Third partyScreenshots

Summary

MetricValue
Performance score76
Total page size331.5 KB
Requests35
TTFB127 ms
Fully Loaded972 ms
First Visual Change367 ms
FCP342 ms
LCP342 ms
CLS0.04494696164522644
Total Blocking Time59 ms
Max Potential FID100 ms
CPU long tasks3
Speed Index382 ms
Visual Complete 85%367 ms
Visual Complete 99%600 ms
Last Visual Change967 ms
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.3 sCPU Long Task duration 95 ms
0.4 sDOM Content Loaded Time 313 msmwStartup 319 msFirst Contentful Paint 342 msLCP <P> 342 msFirst Visual Change 367 msVisual Complete 85% 367 msVisual Complete 95% 367 ms
0.5 s
0.6 sVisual Complete 99% 600 ms
0.7 sPage Load Time 623 msCPU Long Task duration 59 ms
0.9 smwCentralNoticeBanner 803 msLayout Shift 0.04479 811 msCPU Long Task duration 100 ms
1 sLayout Shift 0.00016 930 msLast Visual Change 967 msFully Loaded 972 ms
| 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 254 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 21 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 88.2 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 207.9 kB and the uncompressed size is 746.7 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
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:
  • 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 9 responses that sets both a max-age and expires header. There are 35 responses that sets a server header. 53
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
TitleWikipedia, the free encyclopedia
GeneratorMediaWiki 1.37.0-wmf.6
Width1350
Height2580
DOM elements993
Avg DOM depth11
Max DOM depth19
Iframes0
Script tags6
Local storage519.1 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 Change367 ms
Speed Index382 ms
Visual Complete 85%367 ms
Visual Complete 95%367 ms
Visual Complete 99%600 ms
Last Visual Change967 ms
Visual Readiness600 ms

Browser Metrics

Navigation Timing
backEndTime127 ms
domContentLoadedTime313 ms
domInteractiveTime313 ms
domainLookupTime3 ms
frontEndTime475 ms
pageDownloadTime20 ms
pageLoadTime623 ms
redirectionTime0 ms
serverConnectionTime65 ms
serverResponseTime69 ms
Google Web Vitals
First Contentful Paint (FCP)342 ms
Largest Contentful Paint (LCP)342 ms
Cumulative Layout Shift (CLS)0.04
Total Blocking Time (TBT)59 ms
Extra timings
First Contentful Paint (FCP)342 ms
First Paint342 ms
Largest Contentful Paint (LCP)342 ms
Load Event End623 ms
Fully loaded972 ms
User Timing marks
mwStartup319 ms
mwCentralNoticeBanner803 ms

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 342 ms
Load time0 ms
Size (width*height)180596
DOM path
div#content > div#bodyContent > div#mw-content-text > div:eq(0) > table#mp-upper > tbody > tr > td#mp-left > div#mp-tfa > p> div#content > div#bodyContent > div#mw-content-text > div:eq(0) > table#mp-upper > tbody > tr > td#mp-left > div#mp-tfa > p>
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.04495 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.04479<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"></div>
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
Documents5
Frames5
JSEventListeners37
LayoutObjects1717
MediaKeySessions0
MediaKeys0
Nodes2118
Resources26
ContextLifecycleStateObservers12
V8PerContextDatas1
WorkerGlobalScopes0
UACSSResources0
RTCPeerConnections0
ResourceFetchers5
AdSubframes0
DetachedScriptStates0
ArrayBufferContents0
LayoutCount12
RecalcStyleCount16
LayoutDuration74
RecalcStyleDuration41
DevToolsCommandDuration11
ScriptDuration328
V8CompileDuration5
TaskDuration681
TaskOtherDuration222
ThreadTime1
ProcessTime1
JSHeapUsedSize3714964
JSHeapTotalSize5816320
FirstMeaningfulPaint342
| 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 requests35
Total domains4
Total transfer size331.5 KB
Total content size954.1 KB
Responses missing compression8
Number of cookies3
Third party cookies0
Requests per response code
20035

Largest assets on the page (by transfer size)

URLTypeTransfer SizeContent Size
https://en.wikipedia...ia.org/w/load.phpjavascript138.4 KB505.7 KB
https://upload.wikim...xionOfStJulia.jpgimage36.1 KB35.8 KB
https://en.wikipedia...ia.org/w/load.phpjavascript21.4 KB65.8 KB
https://en.wikipedia...ia.org/w/load.phpjavascript19.5 KB75.3 KB
https://en.wikipedia.org/wiki/Main_Pagehtml19.3 KB76.9 KB
https://en.wikipedia...ia.org/w/load.phpjavascript15.3 KB55.4 KB
https://upload.wikim..._Cropped_2013.jpgimage10.0 KB9.8 KB
https://en.wikipedia...-logos/enwiki.pngimage8.6 KB8.4 KB
https://en.wikipedia...ia.org/w/load.phpcss8.5 KB38.2 KB
https://upload.wikim...mpire-map.svg.pngimage7.8 KB7.1 KB
https://en.wikipedia...ia.org/w/load.phpjavascript7.1 KB25.1 KB
https://upload.wikim...Library_1908c.jpgimage6.5 KB6.3 KB
https://en.wikipedia...ia.org/w/load.phpcss4.4 KB16.5 KB
https://upload.wikim...ttu_Saalasti.jpegimage4.3 KB4.1 KB
https://upload.wikim...news-logo.svg.pngimage2.5 KB2.4 KB
https://upload.wikim...cies-logo.svg.pngimage2.5 KB2.3 KB
https://upload.wikim...2020-icon.svg.pngimage2.0 KB1.8 KB
https://upload.wikim...urce-logo.svg.pngimage1.7 KB1.5 KB
https://upload.wikim...%29_local.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 b19.3 KB76.9 KB1
css0 b12.9 KB54.7 KB2
javascript0 b203.1 KB729.2 KB7
image0 b93.3 KB89.1 KB20
svg0 b1.6 KB1.5 KB4
favicon0 b1.2 KB2.7 KB1
Total0 b331.5 KB954.1 KB35

Size and requests per domain

DomainHeader SizeTransfer SizeContent SizeRequests
en.wikipedia.orgN/A245.3 KB871.3 KB14
upload.wikimedia.orgN/A84.7 KB80.7 KB19
login.wikimedia.orgN/A451 B236 B1
meta.wikimedia.orgN/A945 B1.8 KB1

Expires and last modified statistics

typeminmedianmax
Expires0 seconds0 seconds1 year
Last modified2 seconds23 weeks8 years

Requests loaded after onLoad event

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript20.8 KB3
image2.7 KB2
font0 b0
favicon1.2 KB1
svg650 B1
Total25.4 KB7

Requests loaded after onContentLoad

Includes requests done after onLoad.

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript181.6 KB6
image19.1 KB13
font0 b0
favicon1.2 KB1
svg650 B1
Total202.6 KB21
| 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 59
Max Potential First Input Delay 100
Long Tasks before First Paint195
Long Tasks before First Contentful Paint195
Long Tasks after Load Event End2159
Total Long Tasks3254

Individual Long Tasks

namestartTimedurationcontainerIdcontainerNamecontainerSrccontainerType
unknown21795window
self62459window
self821100window

CPU time spent

Calculated using Tracium.

Categories (ms)
parseHTML22
styleLayout117
paintCompositeRender41
scriptParseCompile5
scriptEvaluation334
garbageCollection12
other144
Events (ms)
V8.Execute211
RunTask139
V8.HandleInterrupts100
Layout74
UpdateLayoutTree42
ParseHTML20
UpdateLayerTree13
Paint12

Time spent per request

URLCPU time (ms)
https://en.wikipedia.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector298
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.cx.eventlogging.campaigns%7Cext.eventLogging%2CnavigationTiming%2Cpopups%2CwikimediaEvents%7Cext.growthExperiments.SuggestedEditSession%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%2CvisibleTimeout%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=1cf9t174

CPU time spent

Tool/domainTime (ms)
en.wikipedia.org472.0
| 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 b19.3 KB76.9 KB1
css0 b12.9 KB54.7 KB2
javascript0 b203.1 KB729.2 KB7
image0 b93.3 KB89.1 KB20
font0 b0 b0 b0
svg0 b1.6 KB1.5 KB4
favicon0 b1.2 KB2.7 KB1
TotalN/A331.5 KB954.1 KB35

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 | layoutShift.png | largestContentfulPaint.png | 

Screenshots

afterPageCompleteCheck.png

afterPageCompleteCheck.png

layoutShift.png

layoutShift.png

largestContentfulPaint.png

largestContentfulPaint.png