Page summary

https://www.wikipedia.org

Tested 2025-02-20 15:04:46 using Chrome 133.0.6943.53 (runtime settings).

SummaryWaterfall MetricsVideoFilmstrip CoachPageXrayCPU
| Summary | | Download Video | Download Timeline Log | Download HAR | Download Console Logs | 

Summary

MetricValue
Page metrics
Performance Score97
Total Page Transfer Size71.5 KB
Requests7
Timing metrics
TTFB [median]489 ms
First Paint [median]928 ms
Fully Loaded [median]999 ms
Google Web Vitals
TTFB [median]489 ms
First Contentful Paint (FCP) [median]928 ms
Largest Contentful Paint (LCP) [median]928 ms
Cumulative Layout Shift (CLS) [median]0.00
CPU metrics
CPU long tasks [median]2
CPU longest task duration263 ms
CPU last long task happens at600 ms
Visual Metrics
First Visual Change [median]933 ms
Speed Index [median]1.198 s
Visual Complete 85% [median]933 ms
Visual Complete 99% [median]9.266 s
Last Visual Change [median]10.800 s
Screenshot of run 1

Timings Summary

Metricminmedianmeanmax
Visual Metrics
FirstVisualChange900 ms933 ms926 ms933 ms
LastVisualChange10.800 s10.800 s10.800 s10.800 s
SpeedIndex1.198 s1.198 s1.334 s1.880 s
LargestImage900 ms933 ms926 ms933 ms
Heading933 ms933 ms953 ms1.033 s
LargestContentfulPaint900 ms933 ms926 ms933 ms
LastMeaningfulPaint933 ms933 ms953 ms1.033 s
VisualReadiness9.867 s9.867 s9.874 s9.900 s
VisualComplete85933 ms933 ms953 ms1.033 s
VisualComplete95933 ms933 ms2.233 s7.433 s
VisualComplete997.433 s9.266 s8.899 s9.266 s
Google Web Vitals
Time To First Byte (TTFB)488 ms489 ms495 ms504 ms
Largest Contentful Paint (LCP)908 ms928 ms928 ms944 ms
First Contentful Paint (FCP)908 ms928 ms928 ms944 ms
Cumulative Layout Shift (CLS)0.00030.00030.00030.0003
More metrics
firstPaint908 ms928 ms928 ms944 ms
loadEventEnd881 ms896 ms912 ms990 ms
CPU
Total Blocking Time0 ms0 ms0 ms0 ms
Max Potential FID0 ms0 ms0 ms0 ms
CPU long tasks 2222
CPU last long task happens at597 ms600 ms605 ms615 ms
| Waterfall | | Download HAR | 

Waterfall

Run 1 SpeedIndex median

| Video | Download | 

Video

Download video
| Filmstrip | 

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s
0.6 sCPU Long Task duration 82 msCPU Long Task duration 256 ms
0.9 sLayout Shift 0.00031 851 msDOM Content Loaded Time 877 msPage Load Time 885 ms
1 sFirst Contentful Paint 928 msLCP <IMG> 928 msFirst Visual Change 933 msVisual Complete 85% 933 msVisual Complete 95% 933 msLargest Image 933 msHeading 933 msFully Loaded 991 ms
1.1 s
1.2 s
1.8 s
2.4 s
3 s
3.6 s
4.2 s
4.8 s
5.4 s
6 s
6.6 s
7.2 s
7.8 s
8.4 s
9 s
9.3 sVisual Complete 99% 9.266 s
9.4 s
9.6 s
10.2 s
10.8 sLast Visual Change 10.800 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. Tested using Coach-core version 8.1.1.

I am the coach

Coach score

Performance advice (97)

TitleAdviceScore
Avoid slowing down the critical rendering path (avoidRenderBlocking)The page has 1 blocking requests and 1 in body parser blocking (2 JavaScript and 0 CSS).80
Description: The critical rendering path is what the browser needs to do to start rendering the page. Every file requested inside of the head element will postpone the rendering of the page, because the browser need to do the request. Avoid loading JavaScript synchronously inside of the head (you should not need JavaScript to render the page), request files from the same domain as the main document (to avoid DNS lookups) and inline CSS for really fast rendering and a short rendering path.
Offenders:
  • https://www.wikipedia.org/portal/wikipedia.org/assets/js/index-6bf78c58fd.js
  • https://www.wikipedia.org/portal/wikipedia.org/assets/js/gt-ie9-ce3fe8e88d.js
  • Have a fast largest contentful paint (largestContentfulPaint) You can add fetchPriority="high" to the image to increase the load priority in Chrome.95
    Description: Largest contentful paint is one of Google Web Vitals and reports the render time of the largest image or text block visible within the viewport, relative to when the page first started loading. To be fast according to Google, it needs to render before 2.5 seconds and results over 4 seconds is poor performance.
    Avoid CPU Long Tasks (longTasks)The page has 2 CPU long tasks with the total of 338 ms. The total blocking time is 0 ms and 2 long tasks before first contentful paint with total time of 338 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 tasks.60
    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. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler.
    Offenders:
  • unknown
  • unknown
  • Long cache headers is good (cacheHeadersLong)The page has 5 requests that have a shorter cache time than 30 days (but still a cache time).95
    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:
  • https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikipedia-logo-v2.png
  • https://www.wikipedia.org/portal/wikipedia.org/assets/img/sprite-de847d1a.svg
  • https://www.wikipedia.org/portal/wikipedia.org/assets/js/index-6bf78c58fd.js
  • https://www.wikipedia.org/portal/wikipedia.org/assets/js/gt-ie9-ce3fe8e88d.js
  • https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikinews-logo_sister.png
  • Best practice advice (100)

    Your best practice score is perfect!

    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:
  • https://www.wikipedia.org/
  • 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:
  • https://www.wikipedia.org/
  • Page info

    Page info
    TitleWikipedia
    Width1904
    Height1193
    DOM elements1046
    Avg DOM depth9
    Max DOM depth12
    Iframes0
    Script tags4
    Local storage94 B
    Session storage0 b
    Network Information API4g
    Resource Hints
    preconnect
    https://upload.wikimedia.org/
    https://en.wikipedia.org/

    Technologies used to build the page.

    Data collected using Wappalyzer version 6.10.66. With updated code from Webappanalyzer 2024-12-27. Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyzer find more information about technologies used.

    TechnologyConfidenceCategory
    Apache Traffic Server 9.2.6100  Web servers
    HSTS 100  Security
    | Browser metrics | Visual Metrics | Largest Contentful Paint | Cumulative Layout Shift | Long Aninimation Frames | Visual Elements | Server timings | 

    Data from run 1

    Visual Metrics

    Browser Metrics

    Google Web Vitals
    Time to first byte (TTFB)489 ms
    First Contentful Paint (FCP)928 ms
    Largest Contentful Paint (LCP)928 ms
    Cumulative Layout Shift (CLS)0.00
    Total Blocking Time (TBT)0 ms
    First Contentful Paint info
    Elements that needed recalculate style before FCP1750
    Time spent in recalculate style before FCP18.167 ms
    Extra timings
    TTFB489 ms
    First Paint928 ms
    Load Event End885 ms
    Fully loaded991 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 typeIMG
    Element/tag<img class="central-featured-logo" src="portal/wikipedia.org/assets/img/Wikipedia-logo-v2.png" srcset="portal/wikipedia.org/assets/img/Wikipedia-logo-v2@1.5x.png 1.5x, portal/wikipedia.org/assets/img/Wikipedia-logo-v2@2x.png 2x" width="200" height="183" alt="">
    Render time 928 ms
    Element render delay310 ms
    TTFB489 ms
    Resource delay7 ms
    Resource load duration122 ms
    Elements that needed recalculate style before LCP1750
    Time spent in recalculate style before LCP18.167 ms
    Load time854 ms
    URL https://www.wikipedi...pedia-logo-v2.png
    Size (width*height)36600
    DOM path
    main > div:eq(0) > img> main > div:eq(0) > img>
    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.

    The Largest Contentful Paint API highlighted this image as a part of the LCP.

    LCP

    Detected Cumulative Layout Shift

    0.00031 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.00031<div class="central-textlogo"></div>,<img class="central-featured-logo" src="portal/wikipedia.org/assets/img/Wikipedia-logo-v2.png" srcset="portal/wikipedia.org/assets/img/Wikipedia-logo-v2@1.5x.png 1.5x, portal/wikipedia.org/assets/img/Wikipedia-logo-v2@2x.png 2x" width="200" height="183" alt="">,<div role="search" class="search-container"></div>,<button class="pure-button pure-button-primary-progressive" type="submit"></button>,<button id="js-lang-list-button" aria-expanded="false" aria-controls="js-lang-lists" class="lang-list-button"></button>
    body#www-wikipedia-org > main > div:eq(0),body#www-wikipedia-org > main > div:eq(0) > img,body#www-wikipedia-org > main > div:eq(1),body#www-wikipedia-org > main > div:eq(1) > form#search-form > fieldset > button,body#www-wikipedia-org > main > nav:eq(1) > div:eq(0) > button#js-lang-list-button
    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.

    Long Animation Frames

    Read more about the Long Animation Frames API here here.

    The top 10 longest animation frames entries

    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    203.8 ms260.6 ms3.1 ms3.1 ms0 ms
    No availible script information.
    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    36.9 ms12.6 ms81.1 ms80.5 ms0.6 ms
    No availible script information.

    Server timings

    namedurationdescription
    cache0hit-front
    host0cp3067

    Custom metrics collected through JavaScript

    There are no custom configured scripts.

    Extra metrics collected using scripting

    There are no custom extra metrics from scripting.

    Visual Elements

    NameDisplay TimeX YWidthHeight
    LargestImage (Wikipedia-logo-v2.png)933 ms 852 198 200 183
    <img class="central-featured-logo" src="portal/wikipedia.org/assets/img/Wikipedia-logo-v2.png" srcset="portal/wikipedia.org/assets/img/Wikipedia-logo-v2@1.5x.png 1.5x, portal/wikipedia.org/assets/img/Wikipedia-logo-v2@2x.png 2x" width="200" height="183" alt="">
    Heading933 ms 864 52 176 69
    <h1 class="central-textlogo-wrapper"></h1>
    LargestContentfulPaint (Wikipedia-logo-v2.png)933 ms 852 198 200 183
    <img class="central-featured-logo" src="portal/wikipedia.org/assets/img/Wikipedia-logo-v2.png" srcset="portal/wikipedia.org/assets/img/Wikipedia-logo-v2@1.5x.png 1.5x, portal/wikipedia.org/assets/img/Wikipedia-logo-v2@2x.png 2x" width="200" height="183" alt="">
    | Summary  | Largest responses  | Requests and sizes per content type  | Data per domain | Expires and last modified statistics  | Requests loaded after onLoad event  | Render blocking requests  | 

    PageXray

    How the page is built.

    Summary
    HTTP versionHTTP/2.0
    Total requests7
    Total domains1
    Total transfer size71.5 KB
    Total content size179.5 KB
    Responses missing compression3
    Number of cookies1
    Third party cookies0
    Requests per response code
    2007

    Largest assets on the page (by transfer size)

    Requests and sizes per content type

    ContentHeader SizeTransfer SizeContent SizeRequests
    html0 b22.5 KB87.4 KB1
    javascript0 b9.8 KB22.5 KB2
    image0 b18.9 KB17.5 KB2
    svg0 b18.6 KB49.4 KB1
    favicon0 b1.7 KB2.7 KB1
    Total0 b71.5 KB179.5 KB7

    Data per domain

    DomainTotal download timeTransfer SizeContent SizeRequests
    www.wikipedia.org1.297 s71.5 KB179.5 KB7

    Expires and last modified statistics

    typeminmedianmax
    Expires1 hour1 day1 year
    Last modified1 week21 weeks21 weeks

    Requests loaded after onLoad event

    Included requests done after load event end.

    ContentTransfer SizeRequests
    html0 b0
    css0 b0
    javascript0 b0
    image0 b0
    font0 b0
    favicon1.7 KB1
    Total1.7 KB1

    Requests loaded after onContentLoad

    Includes requests done after DOM content loaded.

    ContentTransfer SizeRequests
    html0 b0
    css0 b0
    javascript0 b0
    image0 b0
    font0 b0
    favicon1.7 KB1
    Total1.7 KB1

    Render blocking requests

    Render blocking information directly from Chrome.

    BlockingIn body parser blockingPotentially blocking
    110

    Render information

    CPU Long Tasks | CPU Time Spent | 

    CPU

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

    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 0
    Max Potential First Input Delay 0
    Long Tasks before First Paint2338
    Long Tasks before First Contentful Paint2338
    Long Tasks before Largest Contentful Paint2338
    Long Tasks after Load Event End00
    Total Long Tasks2338

    CPU last long task happened at 597 ms

    Individual Long Tasks

    namestartTimedurationcontainerIdcontainerNamecontainerSrccontainerType
    unknown50582window
    unknown597256window

    CPU time spent

    Calculated using Tracium.

    Categories (ms)
    parseHTML15
    styleLayout338
    paintCompositeRender5
    scriptParseCompile1
    scriptEvaluation11
    garbageCollection2
    other72
    Events (ms)
    Layout320
    RunTask43
    UpdateLayoutTree18
    CpuProfiler::StartProfiling10