Run 3 summary

https://www.wikipedia.org

Tested 2025-01-17 22:20:17 using Chrome 131.0.6778.85 (runtime settings).

SummaryWaterfall MetricsVideoFilmstrip CoachPageXrayCPU Screenshots

Summary

MetricValue
Page metrics
Performance score96
Total page size90.9 KB
Requests7
Timing metrics
TTFB407 ms
First Paint839 ms
Fully Loaded3.212 s
Google Web Vitals
TTFB407 ms
First Contentful Paint (FCP) 839 ms
Largest Contentful Paint (LCP) 839 ms
Cumulative Layout Shift (CLS) 0.00
352 ms
Total Blocking Time1.983 s
Max Potential FID1.233 s
CPU metrics
CPU long tasks3
CPU last long task happens at2.112 s
Visual Metrics
First Visual Change866 ms
Speed Index2.973 s
Visual Complete 85%3.066 s
Visual Complete 99%7.033 s
Last Visual Change13.266 s
Screenshot
| Waterfall | | Download HAR | 

Waterfall

| Video | Download | 

Video

Download video
| Filmstrip | 

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s
0.5 sCPU Long Task duration 262 ms
0.9 sFirst Contentful Paint 839 msLCP <SPAN> 839 msCPU Long Task duration 1.233 sFirst Visual Change 866 msLargest Image 866 ms
1 s
1.1 s
1.2 s
1.3 s
1.4 s
1.5 s
1.6 s
1.7 s
1.8 s
1.9 s
2 s
2.1 s
2.2 sCPU Long Task duration 850 ms
2.3 s
3 s
3.1 sDOM Content Loaded Time 3.065 sVisual Complete 85% 3.066 sHeading 3.066 sPage Load Time 3.096 s
3.2 s
3.3 sFully Loaded 3.212 s
3.4 s
3.8 s
4.3 s
4.8 s
5.3 s
5.8 s
6.3 s
6.8 s
7.1 sVisual Complete 95% 7.033 sVisual Complete 99% 7.033 s
7.2 s
7.3 s
7.8 s
8.3 s
8.8 s
9.3 s
9.8 s
10.3 s
10.8 s
11.3 s
11.8 s
12.3 s
12.8 s
13.3 sLast Visual Change 13.266 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.0.2.

I am the coach

Coach score

Performance advice (96)

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-24c3e2ca18.js
  • https://www.wikipedia.org/portal/wikipedia.org/assets/js/gt-ie9-ce3fe8e88d.js
  • Don't scale images in the browser (avoidScalingImages)The page has 1 image that are scaled more than 100 pixels. It would be better if those images are sent so the browser don't need to scale them.90
    Description: It's easy to scale images in the browser and make sure they look good in different devices, however that is bad for performance! Scaling images in the browser takes extra CPU time and will hurt performance on mobile. And the user will download extra kilobytes (sometimes megabytes) of data that could be avoided. Don't do that, make sure you create multiple version of the same image server-side and serve the appropriate one.
    Offenders:
  • https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikipedia-logo-v2@2x.png
  • Avoid CPU Long Tasks (longTasks)The page has 3 CPU long tasks with the total of 2.345 s. The total blocking time is 1.983 s and 1 long task before first contentful paint with total time of 262 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.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. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler.
    Offenders:
  • unknown
  • 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@2x.png
  • https://www.wikipedia.org/portal/wikipedia.org/assets/img/sprite-de847d1a.svg
  • https://www.wikipedia.org/portal/wikipedia.org/assets/js/index-24c3e2ca18.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@2x.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
    Width360
    Height1690
    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 Wappalyzerversion 6.10.66.  Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyser 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 | Interaction To Next Paint | Long Aninimation Frames | Visual Elements | Metrics from CDP | Server timings | 

    Visual Metrics

    Browser Metrics

    Google Web Vitals
    Time to first byte (TTFB)407 ms
    First Contentful Paint (FCP)839 ms
    Largest Contentful Paint (LCP)839 ms
    Interaction to next paint (INP)352 ms
    Total Blocking Time (TBT)1.983 s
    First Contentful Paint info
    Elements that needed recalculate style before FCP343
    Time spent in recalculate style before FCP35.402 ms
    Extra timings
    TTFB407 ms
    First Paint839 ms
    Load Event End3.096 s
    Fully loaded3.212 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 typeSPAN
    Element/tag<span class="central-textlogo__image sprite svg-Wikipedia_wordmark"></span>
    Render time 839 ms
    Elements that needed recalculate style before LCP343
    Time spent in recalculate style before LCP35.402 ms
    Load time808 ms
    URL https://www.wikipedi...rite-de847d1a.svg
    Size (width*height)3750
    DOM path
    main > div:eq(0) > h1 > span> main > div:eq(0) > h1 > span>
    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

    No layout shift detected.

    Interaction to Next Paint

    Interaction to Next Paint (INP) is a metric that try to measure responsiveness. It's useful if you are testing user journeys. Read more about Interaction to Next Paint.

    The measured latency was 352 ms.

    Event typemouseover
    Element typeDIV
    Element class namecentral-featured-lang lang2
    Event target#www-wikipedia-org>main>nav.central-featured>div.central-featured-lang.lang2
    Load state when the event happenedloading

    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
    1.183 s1.217 s25.7 ms5.7 ms20 ms
    No availible script information.
    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    800 ms847.9 ms27.1 ms7.1 ms20 ms
    No availible script information.
    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    218 ms8.2 ms260.8 ms253.7 ms7.1 ms
    No availible script information.
    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    16 ms62.7 ms15.3 ms1.4 ms13.9 ms
    No availible script information.
    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    0 ms65.1 ms5.9 ms0 ms5.9 ms
    No availible script information.
    Blocking duration Work durationRender durationPreLayout DurationStyle And Layout Duration
    0 ms74.8 ms14.2 ms5 ms9.2 ms
    https://www.wikipedia.org/portal/wikipedia.org/assets/js/index-24c3e2ca18.js

    Invoker:  https://www.wikipedia.org/portal/wikipedia.org/assets/js/index-24c3e2ca18.js
    Invoker Type: classic-script
    Window attribution: self

    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.

    CDP Performance

    namevalue
    AudioHandlers0
    AudioWorkletProcessors0
    Documents6
    Frames2
    JSEventListeners27
    LayoutObjects1855
    MediaKeySessions0
    MediaKeys0
    Nodes3202
    Resources6
    ContextLifecycleStateObservers13
    V8PerContextDatas3
    WorkerGlobalScopes0
    UACSSResources0
    RTCPeerConnections0
    ResourceFetchers6
    AdSubframes0
    DetachedScriptStates2
    ArrayBufferContents1
    LayoutCount10
    RecalcStyleCount10
    LayoutDuration2177
    RecalcStyleDuration135
    DevToolsCommandDuration275
    ScriptDuration52
    V8CompileDuration5
    TaskDuration3044
    TaskOtherDuration400
    ThreadTime15
    ProcessTime17
    JSHeapUsedSize2088560
    JSHeapTotalSize3694592
    FirstMeaningfulPaint2094

    Visual Elements

    NameDisplay TimeX YWidthHeight
    LargestImage (Wikipedia-logo-v2.png)866 ms 69 45 57 52
    <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="">
    Heading3.066 s 129 44 152 53
    <h1 class="central-textlogo-wrapper"></h1>
    LargestContentfulPaint866 ms 131 47 150 25
    <span class="central-textlogo__image sprite svg-Wikipedia_wordmark"></span>
    | Summary  | Largest responses  | Requests and sizes per content type  | Data per domain | Expires and last modified statistics  | Console log  | 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 size90.9 KB
    Total content size191.1 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 b19.5 KB77.0 KB1
    javascript0 b9.7 KB22.1 KB2
    image0 b41.4 KB39.9 KB2
    svg0 b18.6 KB49.4 KB1
    favicon0 b1.7 KB2.7 KB1
    Total0 b90.9 KB191.1 KB7

    Data per domain

    DomainTotal download timeTransfer SizeContent SizeRequests
    www.wikipedia.org1.345 s90.9 KB191.1 KB7

    Expires and last modified statistics

    typeminmedianmax
    Expires1 hour1 day1 year
    Last modified2 weeks16 weeks16 weeks

    Console log

    No console log messages.

    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 Time Spent Per Request | 

    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 1983
    Max Potential First Input Delay 1233
    Long Tasks before First Paint1262
    Long Tasks before First Contentful Paint1262
    Long Tasks before Largest Contentful Paint1262
    Long Tasks after Load Event End00
    Total Long Tasks32345

    CPU last long task happened at 2.112 s

    Individual Long Tasks

    namestartTimedurationcontainerIdcontainerNamecontainerSrccontainerType
    unknown491262window
    unknown8541233window
    unknown2112850window

    CPU time spent

    Calculated using Tracium.

    Categories (ms)
    parseHTML50
    styleLayout2342
    paintCompositeRender45
    scriptParseCompile5
    scriptEvaluation73
    garbageCollection0
    other443
    Events (ms)
    Layout2192
    RunTask224
    UpdateLayoutTree151
    CpuProfiler::StartProfiling102
    ParseHTML47
    v8.run33
    Paint31
    Commit26
    PrePaint22
    DecodedDataDocumentParser::AppendBytes22
    RunMicrotasks17
    FunctionCall15

    Time spent per request

    URLCPU time (ms)
    https://www.wikipedia.org/portal/wikipedia.org/assets/js/index-24c3e2ca18.js47
    afterPageCompleteCheck.jpg | layoutShift.jpg | largestContentfulPaint.jpg | 

    Screenshots

    afterPageCompleteCheck.jpg

    afterPageCompleteCheck.jpg

    layoutShift.jpg

    layoutShift.jpg

    largestContentfulPaint.jpg

    largestContentfulPaint.jpg