Tested 2026-03-11 10:20:56 using Chrome 144.0.7559.59 (runtime settings).
| Metric | Value |
|---|---|
| Page metrics | |
| Performance score | 65 |
| Total page size | 1.4 MB |
| Requests | 57 |
| Timing metrics | |
| TTFB | 681 ms |
| First Paint | 1.160 s |
| Fully Loaded | 2.119 s |
| Google Web Vitals | |
| TTFB | 681 ms |
| First Contentful Paint (FCP) | 1.160 s |
| Largest Contentful Paint (LCP) | 1.192 s |
| Cumulative Layout Shift (CLS) | 0.01 |
| 144 ms | |
| CPU metrics | |
| CPU long tasks | 1 |
| CPU last long task happens at | 921 ms |
| Visual Metrics | |
| First Visual Change | 1.167 s |
| Speed Index | 1.415 s |
| Visual Complete 85% | 1.233 s |
| Visual Complete 99% | 4.667 s |
| Last Visual Change | 4.667 s |
Use--filmstrip.showAll to show all filmstrips.
0 s1 sCPU Long Task duration 86 ms1.1 sDOM Content Loaded Time 1.073 s
1.2 sPage Load Time 1.141 sFirst Contentful Paint 1.160 sFirst Visual Change 1.167 sLCP <DIV> 1.192 s
1.3 sVisual Complete 85% 1.233 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 sFully Loaded 2.119 sLayout Shift 0.00033 2.134 sLayout Shift 0.00044 2.149 sLayout Shift 0.00068 2.165 sLayout Shift 0.00085 2.182 sLayout Shift 0.00260 2.199 s
2.3 sLayout Shift 0.00142 2.215 sLayout Shift 0.00138 2.232 sLayout Shift 0.00314 2.249 sLayout Shift 0.00128 2.265 sVisual Complete 95% 2.267 sLayout Shift 0.00094 2.283 sLayout Shift 0.00058 2.299 s
2.4 s
2.5 s
2.6 s
2.7 s
2.8 s
2.9 s
3 s
3.1 s
3.2 s
3.3 s
3.4 s
3.5 s
3.6 s
3.7 s
4.1 s
4.2 s
4.3 s
4.4 s
4.5 s
4.6 s
4.7 sLast Visual Change 4.667 sVisual Complete 99% 4.667 sThe 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.3.
| Title | Advice | Score | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Don't scale images in the browser (avoidScalingImages) | The page has 4 images 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. | 60 | |||||||||
| 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: | |||||||||||
| 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 using more than one jQuery version per page (jquery) | The page uses 2 versions of jQuery! You only need one version, please remove the unnecessary version(s). | 0 | |||||||||
| Description: There are sites out there that use multiple versions of jQuery on the same page. You shouldn't do that because the user will then unnecessarily download extra data. Cleanup the code and make sure you only use one version. | |||||||||||
| Offenders: | |||||||||||
| Avoid CPU Long Tasks (longTasks) | The page has 1 CPU long task with the total of 86 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 86 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. | 80 | |||||||||
| 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: | |||||||||||
| Avoid Frontend single point of failures (spof) | The page has 2 requests inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head. | 80 | |||||||||
| Description: A page can be stopped from loading in the browser if a single JavaScript, CSS, and in some cases a font, couldn't be fetched or is loading really slowly (the white screen of death). That is a scenario you really want to avoid. Never load 3rd-party components synchronously inside of the head tag. | |||||||||||
| Offenders: | |||||||||||
| Avoid doing redirects (assetsRedirects) | The page has 1 redirect. 1 of the redirects are from the base domain, please fix them! | 90 | |||||||||
| Description: A redirect is one extra step for the user to download the asset. Avoid that if you want to be fast. Redirects are even more of a showstopper on mobile. | |||||||||||
| Offenders: | |||||||||||
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 18 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 155.6 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 36 requests that have a shorter cache time than 30 days (but still a cache time). | 64 | |||||||||
| 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 CSS size shouldn't be too big (cssSize) | The total CSS transfer size is 58.7 kB and uncompressed size is 406.8 kB. That is big and the CSS could most probably be smaller. | 50 | |||||||||
| Description: Delivering a massive amount of CSS to the browser is not the best thing you can do, because it means more work for the browser when parsing the CSS against the HTML and that makes the rendering slower. Try to send only the CSS that is used on that page. And make sure to remove CSS rules when they aren't used anymore. | |||||||||||
| Offenders: | |||||||||||
| Avoid redirecting the main document (documentRedirect) | The main document gets redirected 1 time(s). Remove those redirect and make the page faster! | 0 | |||||||||
| Description: You should never ever redirect the main document, because it will make the page load slower for the user. Well, you should redirect the user if the user tries to use HTTP and there's an HTTPS version of the page. The coach checks for that. :) | |||||||||||
| Offenders: | |||||||||||
| Avoid too many fonts (fewFonts) | The page has 3 font requests. Do you really need them? What value does the fonts give the user? | 70 | |||||||||
| Description: How many fonts do you need on a page for the user to get the message? Fonts can slow down the rendering of content, try to avoid loading too many of them because worst case it can make the text invisible until they are loaded (FOIT—flash of invisible text), best case they will flicker the text content when they arrive. | |||||||||||
| Offenders: | |||||||||||
| Total image size shouldn't be too big (imageSize) | The page total image size is 1.1 MB. It's really big. Is the page using the right format for the images? Can they be lazy loaded? 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 197.2 kB and the uncompressed size is 628.6 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? | |||||||||||
| Offenders: | |||||||||||
| Make each CSS response small (optimalCssSize) | https://museuterrissa.cat/templates/rt_metropolis/css-compiled/bootstrap.css size is 17.8 kB (17833) and that is bigger than the limit of 14.5 kB. https://museuterrissa.cat/templates/rt_metropolis/css-compiled/master-1ec488d8bf5847be4c52ff5bd706bc44.css size is 20.9 kB (20924) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB. | 80 | |||||||||
| Description: Make CSS responses small to fit into the magic number TCP window size of 14.5 KB. The browser can then download the CSS faster and that will make the page start rendering earlier. | |||||||||||
Offenders:
| |||||||||||
| Don't use private headers on static content (privateAssets) | The page has 1 request with private headers. 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: | |||||||||||
| Avoid missing and error requests (responseOk) | The page has 1 error response. The page has 1 response with code 404. | 90 | |||||||||
| Description: Your page should never request assets that return a 400 or 500 error. These requests are never cached. If that happens something is broken. Please fix it. | |||||||||||
| Offenders: | |||||||||||
| Title | Advice | Score |
|---|---|---|
| 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: | ||
| Serve all responses on HTTPS (when you are on HTTPS) (mixedContent) | You need to serve all responses on HTTPS. The page have 1 response using HTTP. That is a privacy and security risk. | 0 |
| Description: You need to make sure that if you are on HTTPS, all responses are on HTTPS so that the content served are secured. | ||
| 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: | ||
| Do not share user data with third parties. (thirdPartyPrivacy) | The page has 4% requests that are 3rd party (2 requests with a size of 67.5 kB). The page also have request to companies that harvest data from users and do not respect users privacy (see https://en.wikipedia.org/wiki/Surveillance_capitalism). The page do 1 survelliance request and uses 1 survelliance tool. | 0 |
| Description: Using third party requests shares user information with that third party. Please avoid that! The project https://github.com/patrickhulce/third-party-web is used to categorize first/third party requests. | ||
| Offenders: | ||
| Page info | |
|---|---|
| Title | Inici - Museu de la Terrissa de Quart |
| Width | 1350 |
| Height | 1368 |
| DOM elements | 295 |
| Avg DOM depth | 11 |
| Max DOM depth | 20 |
| Iframes | 0 |
| Script tags | 20 |
| Local storage | 0 b |
| Session storage | 0 b |
| Network Information API | 4g |
Data collected using Wappalyzer version 6.10.54. 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.
| Technology | Confidence | Category |
|---|---|---|
| Varnish | 100 | Caching |
| LiteSpeed | 100 | Web servers |
| HTTP/3 | 100 | Miscellaneous |
Data collected using Third Party Web 0.26.2
| Cdn |
|---|
| jQuery CDN |
| Google CDN |
| Survelliance |
| Google CDN |
| Visual Metrics | |
|---|---|
| First Visual Change | 1.167 s |
| Speed Index | 1.415 s |
| Visual Complete 85% | 1.233 s |
| Visual Complete 95% | 2.267 s |
| Visual Complete 99% | 4.667 s |
| Last Visual Change | 4.667 s |
| Visual Readiness | 3.500 s |
| Navigation Timing | |
|---|---|
| backEndTime | 681 ms |
| domContentLoadedTime | 1.073 s |
| domInteractiveTime | 1.073 s |
| domainLookupTime | 0 ms |
| frontEndTime | 457 ms |
| pageDownloadTime | 3 ms |
| pageLoadTime | 1.141 s |
| redirectionTime | 205 ms |
| serverConnectionTime | 0 ms |
| serverResponseTime | 463 ms |
| Google Web Vitals | |
|---|---|
| Time to first byte (TTFB) | 681 ms |
| First Contentful Paint (FCP) | 1.160 s |
| Largest Contentful Paint (LCP) | 1.192 s |
| Cumulative Layout Shift (CLS) | 0.01 |
| Interaction to next paint (INP) | 144 ms |
| Total Blocking Time (TBT) | 0 ms |
| Extra timings | |
|---|---|
| TTFB | 681 ms |
| First Paint | 1.160 s |
| Load Event End | 1.161 s |
| Fully loaded | 2.119 s |
When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.
| Element type | DIV |
| Element/tag | <div class="rt-bg2"></div> |
| Render time | 1.192 s |
| Element render delay | 111 ms |
| TTFB | 681 ms |
| Resource delay | 336 ms |
| Resource load duration | 65 ms |
| Load time | 1.104 s |
| URL | https://museuterriss...own/top-image.jpg |
| Size (width*height) | 730350 |
| DOM path | |
| div:eq(0) > div> div:eq(0) > div> | |
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.
0.01364 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.
| Score | HTML Element |
|---|---|
| 0.00314 | <div id="ca_banner" style="bottom: 0px; background: url("https://museuterrissa.cat/modules/mod_cookiesaccept/img/przez_b.png"); border-color: rgb(0, 0, 0); color: rgb(255, 255, 255); display: block;"></div> |
| body > div#ca_banner | |
| 0.00260 | <div id="ca_banner" style="bottom: 0px; background: url("https://museuterrissa.cat/modules/mod_cookiesaccept/img/przez_b.png"); border-color: rgb(0, 0, 0); color: rgb(255, 255, 255); display: block;"></div> |
| body > div#ca_banner | |
| 0.00142 | <div id="ca_banner" style="bottom: 0px; background: url("https://museuterrissa.cat/modules/mod_cookiesaccept/img/przez_b.png"); border-color: rgb(0, 0, 0); color: rgb(255, 255, 255); display: block;"></div> |
| body > div#ca_banner | |
| 0.00138 | <div id="ca_banner" style="bottom: 0px; background: url("https://museuterrissa.cat/modules/mod_cookiesaccept/img/przez_b.png"); border-color: rgb(0, 0, 0); color: rgb(255, 255, 255); display: block;"></div> |
| body > div#ca_banner | |
| 0.00128 | <div id="ca_banner" style="bottom: 0px; background: url("https://museuterrissa.cat/modules/mod_cookiesaccept/img/przez_b.png"); border-color: rgb(0, 0, 0); color: rgb(255, 255, 255); display: block;"></div> |
| body > div#ca_banner | |
| 0.00094 | <div id="ca_banner" style="bottom: 0px; background: url("https://museuterrissa.cat/modules/mod_cookiesaccept/img/przez_b.png"); border-color: rgb(0, 0, 0); color: rgb(255, 255, 255); display: block;"></div> |
| body > div#ca_banner | |
| 0.00085 | <div id="ca_banner" style="bottom: 0px; background: url("https://museuterrissa.cat/modules/mod_cookiesaccept/img/przez_b.png"); border-color: rgb(0, 0, 0); color: rgb(255, 255, 255); display: block;"></div> |
| body > div#ca_banner | |
| 0.00068 | <div id="ca_banner" style="bottom: 0px; background: url("https://museuterrissa.cat/modules/mod_cookiesaccept/img/przez_b.png"); border-color: rgb(0, 0, 0); color: rgb(255, 255, 255); display: block;"></div> |
| body > div#ca_banner | |
| 0.00058 | <div id="ca_banner" style="bottom: 0px; background: url("https://museuterrissa.cat/modules/mod_cookiesaccept/img/przez_b.png"); border-color: rgb(0, 0, 0); color: rgb(255, 255, 255); display: block;"></div> |
| body > div#ca_banner | |
| 0.00044 | <div id="ca_banner" style="bottom: 0px; background: url("https://museuterrissa.cat/modules/mod_cookiesaccept/img/przez_b.png"); border-color: rgb(0, 0, 0); color: rgb(255, 255, 255); display: block;"></div> |
| body > div#ca_banner | |
| 0.00033 | <div id="ca_banner" style="bottom: 0px; background: url("https://museuterrissa.cat/modules/mod_cookiesaccept/img/przez_b.png"); border-color: rgb(0, 0, 0); color: rgb(255, 255, 255); display: block;"></div> |
| body > div#ca_banner | |
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.
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 144 ms.
| Event type | pointerover |
| Element type | IMG |
| Element class name | |
| Event target | #rt-mainbody>div.component-content>div.blog>div.items-leading>div.leading-0>p>img |
| Load state when the event happened | loading |
Read more about the Long Animation Frames API here here.
The top 10 longest animation frames entries
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 38.2 ms | 277.5 ms | 1.4 ms | 0.1 ms | 1.3 ms |
| https://museuterrissa.cat/media/system/js/mootools-core.js | ||||
Forced Style And Layout Duration: 8 ms Invoker: https://museuterrissa.cat/media/system/js/mootools-core.js | ||||
| https://museuterrissa.cat/media/system/js/mootools-more.js | ||||
Invoker: https://museuterrissa.cat/media/system/js/mootools-more.js | ||||
| https://museuterrissa.cat/plugins/system/rokbox/assets/js/rokbox.js | ||||
Invoker: https://museuterrissa.cat/plugins/system/rokbox/assets/js/rokbox.js | ||||
| http://code.jquery.com/jquery-latest.min.js | ||||
Invoker: http://code.jquery.com/jquery-latest.min.js | ||||
| https://ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js | ||||
Invoker: https://ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js | ||||
There are no Server Timings.
There are no custom configured scripts.
There are no custom extra metrics from scripting.
| name | value |
|---|---|
| AudioHandlers | 0 |
| AudioWorkletProcessors | 0 |
| Documents | 6 |
| Frames | 7 |
| JSEventListeners | 71 |
| LayoutObjects | 408 |
| MediaKeySessions | 0 |
| MediaKeys | 0 |
| Nodes | 1299 |
| Resources | 64 |
| ContextLifecycleStateObservers | 31 |
| V8PerContextDatas | 3 |
| WorkerGlobalScopes | 0 |
| UACSSResources | 0 |
| RTCPeerConnections | 0 |
| ResourceFetchers | 6 |
| AdSubframes | 0 |
| DetachedScriptStates | 2 |
| ArrayBufferContents | 0 |
| LayoutCount | 122 |
| RecalcStyleCount | 210 |
| LayoutDuration | 75 |
| RecalcStyleDuration | 45 |
| DevToolsCommandDuration | 10 |
| ScriptDuration | 223 |
| V8CompileDuration | 1 |
| TaskDuration | 702 |
| TaskOtherDuration | 348 |
| ThreadTime | 1 |
| ProcessTime | 2 |
| JSHeapUsedSize | 5759808 |
| JSHeapTotalSize | 9961472 |
| FirstMeaningfulPaint | 1207 |
How the page is built.
| Summary | |
|---|---|
| HTTP version | HTTP/2.0 |
| Total requests | 57 |
| Total domains | 3 |
| Total transfer size | 1.4 MB |
| Total content size | 2.2 MB |
| Responses missing compression | 25 |
| Number of cookies | 2 |
| Third party cookies | 0 |
| Requests per response code | |
|---|---|
| 200 | 55 |
| 303 | 1 |
| 404 | 1 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 29.5 KB | 47.7 KB | 2 |
| css | 0 b | 57.3 KB | 397.3 KB | 12 |
| javascript | 649 B | 192.6 KB | 613.8 KB | 17 |
| image | 0 b | 1.1 MB | 1.1 MB | 21 |
| font | 0 b | 75.6 KB | 75.5 KB | 3 |
| Total | 649 B | 1.4 MB | 2.2 MB | 55 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| museuterrissa.cat | 5.512 s | 1.4 MB | 2.0 MB | 55 |
| code.jquery.com | 149 ms | 32.4 KB | 93.5 KB | 1 |
| ajax.googleapis.com | 171 ms | 33.5 KB | 91.2 KB | 1 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 1 week | 1 year |
| Last modified | 1 year | 11 years | 34 years |
Included requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 23.9 KB | 1 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 1001 B | 1 |
| font | 0 b | 0 |
| Total | 26.2 KB | 3 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 23.9 KB | 1 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 1001 B | 1 |
| font | 0 b | 0 |
| Total | 26.2 KB | 3 |
Third party requests categorised by Third party web version 0.26.2.
| Category | Requests |
|---|---|
| cdn | 2 |
| survelliance | 1 |
| Category | Number of tools |
|---|---|
| cdn | 2 |
| survelliance | 1 |
| cdn (2 requests) |
| jQuery CDN |
| Google CDN |
|
| survelliance (1 requests) |
| Google CDN |
Calculated using .*museuterrissa.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 29.5 KB | 47.7 KB | 2 |
| css | 0 b | 57.3 KB | 397.3 KB | 12 |
| javascript | 0 b | 126.7 KB | 429.0 KB | 15 |
| image | 0 b | 1.1 MB | 1.1 MB | 21 |
| font | 0 b | 75.6 KB | 75.5 KB | 3 |
| Total | N/A | 1.4 MB | 2.0 MB | 55 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 0 b | 0 b | 0 |
| css | 0 b | 0 b | 0 b | 0 |
| javascript | 649 B | 65.9 KB | 184.8 KB | 2 |
| image | 0 b | 0 b | 0 b | 0 |
| font | 0 b | 0 b | 0 b | 0 |
| Total | 648 B | 65.9 KB | 184.8 KB | 2 |
afterPageCompleteCheck.png
layoutShift.png
largestContentfulPaint.png
