Tested 2026-09-24 01:42:57 using Chrome 151.0.7922.75 (runtime settings)
This page is fast to paint and visually stable, but a little janky to interact with, missing some accessibility basics, loose on best practices, weak on user privacy and heavy to download.
Visual metrics
Google Web Vitals
Accessibility · axe-core
The page has 5 blocking requests and 7 in body parser blocking (11 JavaScript and 1 CSS). There are 3 potentially render blocking requests. You need to verify if they are render blocking: https://ikkyu-tea.com/avljl2rk9q5pNTk0OGIyMDQ4NTQ3ZDk0NzBiMTQ4ZjA1/z83nYJsYsGiUFc27fzDk-AfV5ro https://www.googletagmanager.com/gtag/js?id=AW-856208209 https://static.klaviyo.com/onsite/js/U3gmjp/klaviyo.js
The page has 17 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.
The page has 49 images (out of 49) without a decoding hint. Add decoding="async" to non-critical images so the browser can decode them off the main thread.
axe-core flagged 3 high-impact accessibility violations (0 critical, 3 serious). Open the Accessibility tab to see the offending elements.
Timings summary
| Metric | Min | Median | Mean | Max | Runs agree? |
|---|---|---|---|---|---|
| First visual change | 266 ms | 333 ms | 361 ms | 484 ms | runs disagree ±33% |
| Last visual change | 7.781 s | 11.633 s | 10.860 s | 13.166 s | runs disagree ±23% |
| Speed index | 4.723 s | 7.005 s | 6.386 s | 7.431 s | runs disagree ±19% |
| Largest image | 266 ms | 333 ms | 361 ms | 484 ms | runs disagree ±33% |
| Heading | 7.574 s | 11.600 s | 10.780 s | 13.166 s | runs disagree ±24% |
| Last meaningful paint | 7.574 s | 11.600 s | 10.780 s | 13.166 s | runs disagree ±24% |
| Visual readiness | 7.297 s | 11.300 s | 10.499 s | 12.900 s | runs disagree ±25% |
| Visual complete 85 | 6.675 s | 10.466 s | 10.047 s | 13.000 s | runs disagree ±30% |
| Visual complete 95 | 7.159 s | 11.166 s | 10.486 s | 13.133 s | runs disagree ±27% |
| Visual complete 99 | 7.781 s | 11.633 s | 10.860 s | 13.166 s | runs disagree ±23% |
Run 1 SpeedIndex median
The red band on the timeline marks when the main thread was busy with long tasks: moments when the page could not paint or respond, however the video looks.
Download videoUse --filmstrip.showAll to show all filmstrips.
Click a frame to seek the video to that moment. The dot marks frames where the page changed visually.
How smoothly Chrome delivered frames to the screen during the test. Dropped counts only frames Chrome flags as affecting smoothness. On mostly-static pages the longest gap includes idle time where there was simply nothing to draw.
Rendering was not meaningfully delayed. First paint landed at 332 ms on a 34 ms first byte; the 1 render-blocking request was done by 98 ms and the remaining ~234 ms is style and layout work (15 ms of it measured style recalculation). The largest paint followed at 3.856 s.
Style the browser had to recalculate before it could paint: many elements or a lot of time spent here points at expensive CSS on the critical rendering path. The recalculation count and the largest single one tell the two problems apart: one massive style change touching most of the page (few recalculations, the largest close to the total) needs different medicine than thousands of tiny ones (many recalculations, each tiny).
Style recalculation is not holding up your paint. 15 ms of restyling before the page painted, 4.4 % of the time to First Contentful Paint. Nothing here needs attention.
The recalculation work before first paint is 4.4 % of the time to First Contentful Paint.
JavaScript read a layout value (offsetTop, getBoundingClientRect, …) while the page was mid-change, so the browser had to re-layout synchronously, work that blocks rendering. Reflows before First Contentful Paint delayed the first pixels; reflows before Largest Contentful Paint delayed the main content.
That is 0.7 % of the time to Largest Contentful Paint. The number of reflows matters more than the milliseconds: layout thrashing multiplies on slower devices.
See every forced reflow for the whole page load on the CPU tab
Blocking requests delay both paints: the browser renders nothing until they arrive, so they push First Contentful Paint and everything after it, including the largest paint (LCP). Requests that block the parser inside the body stall everything after them in the document. Load JavaScript with defer or async, and keep non-critical CSS off the critical path with media attributes. Bars show when each request loaded on a clock that runs to the last paint (the dashed line is FCP, the clock ends at LCP); the gap after the bars is style and layout work. Web fonts are context, not blockers: text renders invisible or in a fallback face while they load, so a font finishing after a paint is the classic reason text changed late.
| Request | When it loaded | Transfer | Download |
|---|---|---|---|
document | 61 ms | 17.6 KB | 60 ms |
loaded after LCP, at 15.211 s | 311.1 KB | 294 ms | |
loaded after LCP, at 15.211 s | 14.0 KB | 82 ms | |
loaded after LCP, at 15.210 s | 46.6 KB | 80 ms | |
webfont.jsblocking | 21 ms | 5.9 KB | 21 ms |
loaded after LCP, at 15.210 s | 8.6 KB | 15 ms | |
ikkyutea.schunk.009578f6d9774385.jsblocks parser in body | 55 ms | 28.3 KB | 55 ms |
jquery-3.5.1.min.dc5e7f18c8.jsblocks parser in body | 51 ms | 30.4 KB | 51 ms |
ikkyutea.schunk.b8534fd20dd64675.jsblocks parser in body | 44 ms | 8.6 KB | 44 ms |
| 7 more requests | all done by 2.287 s | 394.3 KB | |
LCP resource | 3.543 s | 288.7 KB | 3.543 s |
1.742 s | 98.3 KB | 1.742 s | |
loaded after LCP, at 5.229 s | 9.0 KB | 15 ms | |
loaded after LCP, at 15.843 s | 19.6 KB | 13 ms | |
964 ms1.928 s2.892 sFCP 332 msLCP 3.856 s |
Why the browser had to recalculate style and layout: every DOM/style change invalidates some set of nodes, and the same class or attribute churning over and over is the pattern to hunt. Counts, not milliseconds: the time is in the style recalculation numbers above.
Chase what keeps changing after the page is up. 3 572 style recalculations and 13 479 layout invalidations fired after first paint, on a page the user was already looking at. The biggest driver is attribute class (163×). Start with the script under "Scripts causing invalidations" that keeps triggering it.
attribute: class163×attribute: tabindex84×pseudo: disabled4×pseudo: enabled4×attribute: disabled1×attribute: id1×Invalidations while the largest paint was still pending, so these delayed it.
| Reason | Style recalculations | Layout |
|---|---|---|
| Related style rule | 161 | – |
| JavaScript changed an inline styleSet a class instead of writing element.style, so the browser can batch the work. | 97 | – |
| A node was inserted into the page | 38 | – |
| Frame | 2 | – |
| Style attribute change | 1 | – |
| A web font finished loadingPreload the font or use font-display so a late swap does not re-style the page. | – | 7 140 |
| An element entered layout | – | 907 |
| An element left layout | – | 12 |
| A style change forced layout | – | 34 |
| An element's size changed | – | 9 |
| Unknown | – | 5 |
| An SVG element changed | – | 4 |
| Scrollbar changed | – | 1 |
Churn on the fully rendered page: wasted work and possible jank, but no paint delay.
| Reason | Style recalculations | Layout |
|---|---|---|
| An animation updated stylesAnimate transform and opacity so the compositor can run it off the main thread. | 3 120 | – |
| Related style rule | 26 | – |
| JavaScript changed an inline styleSet a class instead of writing element.style, so the browser can batch the work. | 51 | – |
| A node was inserted into the page | 17 | – |
| An @keyframes rule changed | 49 | – |
| A stylesheet rule changed | 9 | – |
| Frame | 1 | – |
| A web font finished loadingPreload the font or use font-display so a late swap does not re-style the page. | – | 4 912 |
| An element entered layout | – | 301 |
| An element left layout | – | 131 |
| A style change forced layout | – | 16 |
| An element's size changed | – | 1 |
| Child anonymous block changed | – | 6 |
The page being constructed and styled for the first render. Expected work, shown for scale.
| Reason | Style recalculations | Layout |
|---|---|---|
| A node was inserted into the page | 23 | – |
| A stylesheet rule changed | 1 | – |
| An element entered layout | – | 533 |
| An element left layout | – | 3 |
| An element's size changed | – | 20 |
| Unknown | – | 1 |
| An SVG element changed | – | 1 |
2 animations run on the main thread instead of on the browser's fast path that animates without blocking other page work (the compositor); they can make the rendering you see above janky. See them on the CPU tab.
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 9.2.1.
avoidRenderBlockingThe page has 5 blocking requests and 7 in body parser blocking (11 JavaScript and 1 CSS). There are 3 potentially render blocking requests. You need to verify if they are render blocking: https://ikkyu-tea.com/avljl2rk9q5pNTk0OGIyMDQ4NTQ3ZDk0NzBiMTQ4ZjA1/z83nYJsYsGiUFc27fzDk-AfV5ro https://www.googletagmanager.com/gtag/js?id=AW-856208209 https://static.klaviyo.com/onsite/js/U3gmjp/klaviyo.js
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.
avoidScalingImagesThe page has 17 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.
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.
decodingAsyncThe page has 49 images (out of 49) without a decoding hint. Add decoding="async" to non-critical images so the browser can decode them off the main thread.
Setting decoding="async" on an <img> tells the browser it can decode the image off the main thread, which keeps the page responsive to user interactions while images are being processed. The default ("auto") leaves the choice to the browser. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#decoding
googleTagManagerThe page is using Google Tag Manager, this is a performance risk since non-tech users can add JavaScript to your page.
Google Tag Manager makes it possible for non tech users to add scripts to your page that will downgrade performance.
lazyLoadingImagesThe page has 31 below-the-fold images without loading="lazy". Add loading="lazy" so the browser defers downloading and decoding them until the user scrolls them into view.
Adding loading="lazy" to an <img> tells the browser not to download or decode it until it is close to the viewport. For images that the user may never see (deep in the page, behind a tab, in a footer carousel), this saves bandwidth and main-thread time during initial render. The LCP image and any image in the initial viewport should NOT be lazy-loaded — that delays the first paint. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#loading
longTasksThe page has 10 CPU long tasks with the total of 763 ms. The total blocking time is 238 ms and 1 long task before first contentful paint with total time of 75 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.
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.
modernImageFormatsThe page ships 28 images (out of 28) in JPEG/PNG/GIF without a modern alternative. Wrap them in a <picture> with a <source type="image/avif"> or "image/webp" before the legacy <img>, or serve modern formats from your image pipeline directly. AVIF and WebP usually deliver 25–50% smaller files at the same quality.
AVIF and WebP routinely deliver 25–50% smaller files than JPEG and PNG at the same perceived quality, and every browser version still under support understands at least one of them. Ship modern formats either through a <picture> element with <source type="image/avif"> / "image/webp" entries in front of the legacy <img>, or directly from a content-negotiating image pipeline that returns AVIF / WebP when the client accepts it. https://web.dev/articles/serve-images-webp
fewFontsThe page has 30 font requests. Do you really need them? What value does the fonts give the user?
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.
javascriptSizeThe total JavaScript transfer size is 1.5 MB and the uncompressed size is 5.3 MB. This is totally crazy! There is really room for improvement here.
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?
pageSizeThe page total transfer size is 9 MB, which is more than the coach limit of 3 MB. That is insane and you need to make it smaller.
Avoid having pages that have a transfer size over the wire of more than 3 MB (desktop) and 2 MB (mobile) because heavy pages hurt performance and are expensive for users on metered connections. Reference: HTTP Archive median page weight in 2024 was around 2.7 MB desktop / 2.4 MB mobile, so this rule fires when a page is above the modern median.
cacheHeadersThe page has 6 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 67.5 kB the next access.
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.
privateAssetsThe page has 6 requests with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone.
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.
cacheHeadersLongThe page has 55 requests that have a shorter cache time than one year (but still a cache time).
Setting a cache header is good. Setting a long cache header (a year) is even better because the asset will stay in the browser cache across visits. For content-hashed URLs (e.g. app.4af2.css) you can safely use Cache-Control: max-age=31536000, immutable. For unversioned URLs that may change, use a revalidating strategy instead.
spofThe page has 6 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.
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.
cssSizeThe total CSS transfer size is 126.4 kB and uncompressed size is 807.5 kB. That is big and the CSS could most probably be smaller.
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.
imageSizeThe page total image size is 6.3 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/.
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.
largestContentfulPaintLargest contentful paint can be improved 3.856 s. It is in the Google Web Vitals needs improvement range, slower than 2.5 seconds.
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.
optimalCssSizehttps://cdn.prod.website-files.com/5948b2048547d9470b148f05/css/ikkyutea.shared.e7d81c8e1.min.css size is 42.6 kB (42577) and that is bigger than the limit of 25 kB. https://static.zohocdn.com/salesiq/styles/newembedtheme_mMPZDsorCyXTApCS1XHiqGT6LMeTq4cMGpcfep1jUcma__S_CGJUZo9XQCBTPdYX_.css size is 47.7 kB (47709) and that is bigger than the limit of 25 kB. Try to keep each CSS response under 25 kB.
Render-blocking CSS holds up the first paint until it has fully downloaded, parsed and applied, so smaller CSS files mean a faster start. Split your CSS into a small critical bundle inlined or eagerly loaded, with the rest lazy-loaded.
inlineCssThe 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.
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.
mimeTypesThe page has 1 misconfigured mime type.
It's not a great idea to let browsers guess content types (content sniffing), in some cases it can actually be a security risk.
languageThe page is missing a language definition in the HTML tag. Define it with <html lang="YOUR_LANGUAGE_CODE">
According to the W3C recommendation you should declare the primary language for each Web page with the lang attribute inside the <html> tag https://www.w3.org/International/questions/qa-html-language-declarations#basics.
thirdPartyThe page do more requests to third party domains (152 requests and 8.6 MB) then first party (3 requests and 390.7 kB). The page transfer more bytes from third party domains (8.6 MB) then first party (390.7 kB). The regex .*ikkyu-tea.* was used to calculate first/third party requests.
Do not load most of your content from third party URLs.
unnecessaryHeadersThere are 1 response that sets a p3p header. There are 34 responses that sets both a max-age and expires header. There are 5 responses that sets a pragma no-cache header (that is a request header). There are 155 responses that sets a server header.
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.
gaThe page is using Google Analytics meaning you share your users private information with Google. You should use analytics that care about user privacy, something like https://matomo.org.
Google Analytics share private user information with Google that your user hasn't agreed on sharing.
referrerPolicyNo <meta name="referrer"> tag was found on the page. Set a Referrer-Policy response header (preferred) or add a meta tag, for example <meta name="referrer" content="strict-origin-when-cross-origin">.
Without an explicit referrer policy the browser falls back to the user-agent default and may leak the full URL of the previous page (including query strings) to every cross-origin request. Set a Referrer-Policy response header (preferred) or a <meta name="referrer"> tag in the document. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy
surveillanceThe page embeds 2 resources from companies that profit from user surveillance. Consider privacy-respecting alternatives.
Embedding scripts or iframes from companies whose business model is surveillance capitalism (Google, Facebook, etc.) leaks detailed user data on every page view, often before the user has had a chance to consent. See https://en.wikipedia.org/wiki/Surveillance_capitalism for background. Prefer privacy-respecting alternatives where possible.
contentSecurityPolicyHeaderSet a Content-Security-Policy header to mitigate cross-site scripting attacks. You can start with a Content-Security-Policy-Report-Only header, which only reports violations rather than blocking them.
A Content-Security-Policy response header tells the browser which sources of script, style, and other content are allowed. The most effective form is a strict CSP using nonces or hashes together with strict-dynamic; the worst is a missing header, with unsafe-inline and unsafe-eval close behind. https://web.dev/articles/strict-csp
crossOriginEmbedderPolicyHeaderSet a Cross-Origin-Embedder-Policy header (typically require-corp or credentialless) on the document response to control cross-origin embedding.
Cross-Origin-Embedder-Policy (COEP) makes the page refuse to load cross-origin subresources unless they explicitly opt in via CORP or CORS. Together with Cross-Origin-Opener-Policy it puts the page in a cross-origin isolated context, which mitigates cross-window side-channel attacks (Spectre) and unlocks high-resolution timers and SharedArrayBuffer. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy
crossOriginOpenerPolicyHeaderSet a Cross-Origin-Opener-Policy header (typically same-origin) on the document response to isolate the page from cross-origin windows.
Cross-Origin-Opener-Policy (COOP) lets a page sever its window-group ties to cross-origin documents that opened it or that it opens. Together with Cross-Origin-Embedder-Policy it puts the page in a cross-origin isolated context, which mitigates cross-window side-channel attacks (Spectre) and unlocks high-resolution timers and SharedArrayBuffer. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy
crossOriginResourcePolicyHeaderSet a Cross-Origin-Resource-Policy header (same-origin, same-site or cross-origin) on the document response to limit who may embed it.
Cross-Origin-Resource-Policy (CORP) is a per-response opt-in that tells the browser which origins are allowed to embed the resource. It blocks cross-origin or cross-site no-cors embedding (img, script, iframe, etc.) and is one of the building blocks of cross-origin isolation. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Resource-Policy
nelHeaderSet a NEL header (paired with Reporting-Endpoints) to collect connection-level error reports from the field.
The NEL (Network Error Logging) response header tells the browser to record connection-level failures (DNS, TLS, HTTP errors) and ship them to a reporting endpoint. NEL pairs with the Reporting-Endpoints / Report-To header — the page declares the endpoint group and NEL points at it. Together they give you visibility into errors that never reach your origin server. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/NEL
permissionsPolicyHeaderSet a Permissions-Policy header to control which browser features the page can use.
The Permissions-Policy response header (the successor to Feature-Policy) lets a site explicitly opt in or out of powerful browser features such as camera, microphone, geolocation, payment and clipboard. Setting a strict policy reduces the attack surface and limits what embedded third parties can do. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy
referrerPolicyHeaderSet a referrer-policy header to make sure you do not leak user information.
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/.
reportingEndpointsHeaderSet a Reporting-Endpoints header (or the legacy Report-To header) so CSP reports, NEL data and other Reporting-API events have an endpoint to land at.
The Reporting-Endpoints response header (the successor to Report-To) names the URLs that browsers should POST reports to. Without it, CSP report-to directives, Cross-Origin-Opener-Policy reports, NEL data and other Reporting-API events have nowhere to go. The legacy Report-To header is still accepted for older Chromium versions. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Reporting-Endpoints
thirdPartyPrivacyThe page has 46% requests that are 3rd party (72 requests with a size of 1.5 MB). 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 36 survelliance requests and uses 5 survelliance tools. The page do 36 surveillance requests and uses 5 surveillance tools. The page do 2 tag-manager requests and uses 1 tag-manager tool. The page do 38 ad requests and uses 3 ad tools. The page do 2 utility requests and uses 1 utility tool.
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.
xContentTypeOptionsHeaderSet X-Content-Type-Options: nosniff on the document response to prevent MIME-sniffing.
X-Content-Type-Options: nosniff prevents browsers from interpreting files as a different MIME type than what is declared in the Content-Type header. This blocks a class of cross-site scripting and content-type confusion attacks and should be set on every response. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options
strictTransportSecurityHeaderA strict transport header is set but miss out on setting includeSubDomains
The HTTP Strict-Transport-Security response header (often abbreviated as HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security.
A snapshot of what the browser actually built for this page: the document, how big and deep the DOM tree is and what it kept in storage. Big, deep trees are slower to style and lay out, so the counts Chrome warns about carry a flag.
Document
What the page says it is and how large it rendered.
DOM structure
How much markup the browser has to build, style and lay out.
What the page stored on the client, and the network it was tested on.
Data collected using
Coach-core version 9.2.1. With updated code from
Webappanalyzer 2026-05-04. Use
--browsertime.firefox.includeResponseBodies html or
--browsertime.chrome.includeResponseBodies html to help Wappalyzer find more information about technologies used.
Data collected using Third Party Web version 0.29.2.
Data from run 1
0.0s2.6s4.6s6.0s7.5s8.9s10.3s11.7sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > div#hero > div > div#w-slider-mask-0 > div:eq(0)
The LCP element is highlighted in the screenshot. If nothing is highlighted the element was removed before the screenshot or the LCP API couldn't find it.
The Largest Contentful Paint API matched this image:
How much the page's content shifts as it loads, collected via the Cumulative Layout Shift API.
One shift is 59% of your 0.003 CLS. #text moved at 576 ms. Reserve space for whatever renders into that spot, a fixed height or an aspect-ratio box, so later content stops pushing the page around.
Worst first, showing shifts of 0.01 and up. Each percentage is that shift's exact share of the score.
The shift is spread across many movements below 0.01, none large enough to single out. Check the video or filmstrip to see what moved.
Elements that shifted by more than 0.01 are highlighted in the screenshot. If an element shifted outside the viewport, it won't appear here. Check the video or filmstrip to see the shift.
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
| Header | Value |
|---|---|
age | 81638 |
alt-svc | h3=":443"; ma=86400 |
cf-cache-status | HIT |
cf-ray | a3fe1876a9f22068-CDG |
content-encoding | gzip |
content-type | text/html; charset=utf-8 |
date | Thu, 24 Sep 2026 01:42:58 GMT |
last-modified | Wed, 23 Sep 2026 05:26:07 GMT |
link | <https://cdn.prod.website-files.com>; rel=preconnect; crossorigin, <https://cdn.prod.website-files.com/5948b2048547d9470b148f05/css/ikkyutea.shared.e7d81c8e1.min.css>; rel=preload; as=style; crossorigin; integrity="sha384-59gcjhYXFDseQKEra7vc7/eRrznGaR79N+t+zHwe7B2T4oAT7TgwRSTPRdSIw4IU", <https://fonts.googleapis.com>; rel=preconnect, <https://fonts.gstatic.com>; rel=preconnect; crossorigin |
server | cloudflare |
strict-transport-security | max-age=31536000 |
surrogate-control | max-age=432000 |
surrogate-key | ikkyu-tea.com 5948b2048547d9470b148f05 pageId:5c00c9acc661387fea82514d 5c00c9acc661385ce28251f3 |
vary | accept-encoding |
x-lambda-id | 8f7c5736-50a0-453c-ba7f-40482eab3565 |
x-wf-region | us-east-1 |
Transfer size8.6 MB
Content size12.9 MB
Requests155
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 17.6 KB | 68.7 KB | 2 |
| css | 0 b | 123.4 KB | 788.6 KB | 7 |
| javascript | 2.2 KB | 1.4 MB | 5.1 MB | 51 |
| image | 746 B | 6.0 MB | 6.0 MB | 49 |
| font | 0 b | 1015.7 KB | 1.0 MB | 30 |
| svg | 0 b | 8.7 KB | 12.7 KB | 7 |
| plain | 0 b | 548 B | 0 b | 3 |
| json | 0 b | 20.2 KB | 39.7 KB | 5 |
| other | 0 b | 0 b | 0 b | 1 |
| Total | 2.9 KB | 8.6 MB | 12.9 MB | 155 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| ikkyu-tea.com | 4.610 s | 381.5 KB | 1.1 MB | 3 |
| cdn.prod.website-files.com | 114.976 s | 6.2 MB | 6.6 MB | 60 |
| ajax.googleapis.com | 31 ms | 5.9 KB | 12.9 KB | 1 |
| d3e54v103j8qbb.cloudfront.net | 56 ms | 30.4 KB | 87.4 KB | 1 |
| fonts.googleapis.com | 64 ms | 5.9 KB | 155.3 KB | 2 |
| www.googletagmanager.com | 3.415 s | 161.6 KB | 473.6 KB | 2 |
| static.klaviyo.com | 32.579 s | 248.2 KB | 959.8 KB | 25 |
| s.adroll.com | 4.093 s | 134.7 KB | 586.3 KB | 3 |
| fonts.gstatic.com | 8.102 s | 837.3 KB | 836.4 KB | 27 |
| salesiq.zoho.com | 3.894 s | 48.0 KB | 158.9 KB | 1 |
| static-tracking.klaviyo.com | 11.999 s | 23.8 KB | 63.9 KB | 4 |
| region1.analytics.google.com | 144 ms | N/A | 0 b | 1 |
| stats.g.doubleclick.net | 28 ms | 548 B | 0 b | 1 |
| www.google.fr | 31 ms | 63 B | 42 B | 1 |
| www.google.com | 31 ms | N/A | 0 b | 1 |
| ad.doubleclick.net | 33 ms | N/A | 0 b | 1 |
| d.adroll.com | 334 ms | 665 B | 572 B | 1 |
| fast.a.klaviyo.com | 19 ms | 912 B | 1.3 KB | 1 |
| static-forms.klaviyo.com | 43 ms | 3.0 KB | 9.2 KB | 1 |
| salesiq.zohopublic.com | 1.004 s | 15.6 KB | 29.2 KB | 3 |
| a.klaviyo.com | 128 ms | 680 B | 43 B | 1 |
| static.zohocdn.com | 680 ms | 467.4 KB | 1.9 MB | 14 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 1 year | 1 year |
| Last modified | 0 seconds | 1 year | 9 years |
Includes requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 54.2 KB | 2 |
| javascript | 355.1 KB | 6 |
| image | 5.5 KB | 3 |
| font | 19.6 KB | 1 |
| favicon | 0 b | 0 |
| json | 1.3 KB | 1 |
| Total | 435.6 KB | 13 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 1 |
| css | 77.1 KB | 5 |
| javascript | 938.0 KB | 39 |
| image | 7.1 KB | 5 |
| font | 43.1 KB | 3 |
| favicon | 0 b | 0 |
| plain | 548 B | 3 |
| json | 20.2 KB | 5 |
| other | 0 b | 1 |
| Total | 1.1 MB | 62 |
Tasks ≥ 50 ms blocking the main thread, collected via the Long Task API.
A long animation frame (LOAF) is a frame that took ≥ 50 ms from input to the next paint. The part beyond the threshold is blocking time, the number that hurts Interaction to Next Paint and Total Blocking Time. Break long tasks up (scheduler.yield(), smaller chunks) or move the work off the main thread. Read more about the Long Animation Frames API.
| Script | Frames | Time running | Blocking (share by run time) | Forced style & layout | Triggered by |
|---|---|---|---|---|---|
| siqnewchatwindow_IaU5HDdjqUuWknwrJ7bSBCp0zSmf3sPuVNu-KbEyNpKv-E8FrkSxBDY0VRaP8YWA_.js3rd party | 1 | 127.5 ms | 73.4 ms | 1.7 ms | script tag, event handler |
| jquery-3.5.1.min.dc5e7f18c8.js3rd party | 2 | 103.1 ms | 68.9 ms | 16.9 ms | script tag, timer or animation callback |
| z83nYJsYsGiUFc27fzDk-AfV5ro | 2 | 158.2 ms | 65.4 ms | – | script tag, timer or animation callback |
| Render.c23999bf4416b.js3rd party | 1 | 76.5 ms | 28.4 ms | 7.8 ms | script tag |
| ikkyutea.08dfb684.bc87aa21f218a111.js3rd party | 1 | 60.1 ms | 22.8 ms | 0.5 ms | script tag |
| js3rd party | 1 | 64.1 ms | 14 ms | – | script tag |
| z83nYJsYthL6f87FC1OIjQfbEwXaye4HbIwb3kGB0INERua6 | 1 | 65.1 ms | 13.3 ms | – | script tag |
| ikkyutea.schunk.b80b420a8277e4d7.js3rd party | 1 | 5.9 ms | 3.3 ms | 1.9 ms | timer or animation callback |
A frame's blocking time is split between its scripts by their share of the frame's work, capped at each script's own run time — blocking from work no script owns (HTML parsing, browser internals) stays unattributed. The per-script blocking view below uses the same attribution.
The browser did not report which script was responsible for this frame — typically its own style/layout work, or a cross-origin script it will not name.
How much each script blocked the main thread, derived from the Long Animation Frame API. Each frame's blocking time is split between its scripts by their share of the frame's work, capped at each script's own run time — blocking from work no script owns (HTML parsing, browser internals) is not attributed (older data credits the script that started the frame). The closest answer to "which script should I fix to improve TBT" the platform exposes.
Total Blocking Time attributed per script from the Chrome trace: every main-thread task longer than 50 ms blocks input for the remainder, and each blocking task is credited to the script whose own code ran the longest during that task.
All main-thread work during the full page load, not just the share that blocked input. Calculated from the Chrome trace.
parseHTMLstyleLayoutscriptParseCompilescriptEvaluationpaintCompositeRendergarbageCollectionotherHow much setTimeout/setInterval work the page runs, credited to the script that scheduled each timer. Many zero-delay timers mean work sliced into a machine-gun of tiny tasks; repeating timers are polling.
A forced reflow happens when JavaScript reads a layout-triggering property (offsetTop, getBoundingClientRect, …) inside a handler, forcing the browser to synchronously recompute layout. The scripts below caused most of the page's reflows. Fix them in priority order.
Each long animation frame reports how much time each script spent forcing synchronous style and layout, i.e. JavaScript reading layout-triggering properties mid-execution. Same actionable answer as forced reflows above but measured directly by the browser instead of inferred from the trace.
Main-thread CPU time from the Chrome trace split by domain. First party is ikkyu-tea.com.
Animations that fell back from the compositor to the main thread, blocking each frame instead of running on the GPU.
Each chip below is a CSS property the page tried to animate that Chrome couldn't hand to the compositor. Swap it for a transform or opacity equivalent where you can.
margin-left1×background-color1×Want to dig deeper? Download the Chrome trace and drag-and-drop it into Performance in DevTools.
Third party requests categorised by Third party web version 0.29.2.
Requests by category108
Domains that didn't match any tool in Third party web. If you are sure they are third party domains, please do a PR to that project. You can also fine tune the list using --firstParty.
Transfer size8.6 MB
Content size12.9 MB
Requests155
Calculated using .*ikkyu-tea.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 17.6 KB | 68.7 KB | 1 |
| css | 0 b | 0 b | 0 b | 0 |
| javascript | 0 b | 363.9 KB | 1.1 MB | 2 |
| image | 0 b | 0 b | 0 b | 0 |
| font | 0 b | 0 b | 0 b | 0 |
| favicon | 0 b | 0 b | 0 b | 0 |
| Total | N/A | 381.5 KB | 1.1 MB | 3 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 0 b | 0 b | 1 |
| css | 0 b | 123.4 KB | 788.6 KB | 7 |
| javascript | 2.2 KB | 1.1 MB | 4.0 MB | 49 |
| image | 746 B | 6.0 MB | 6.0 MB | 49 |
| font | 0 b | 1015.7 KB | 1.0 MB | 30 |
| favicon | 0 b | 0 b | 0 b | 0 |
| svg | 0 b | 8.7 KB | 12.7 KB | 7 |
| plain | 0 b | 548 B | 0 b | 3 |
| json | 0 b | 20.2 KB | 39.7 KB | 5 |
| other | 0 b | 0 b | 0 b | 1 |
| Total | 2.8 KB | 8.2 MB | 11.8 MB | 152 |
Axe is an accessibility testing engine for websites and other HTML-based user interfaces. Tested using axe-core version 4.11.4. Read more about axe-core.
This page has accessibility issues to fix.
Worst impact across the runs: serious. Open an individual run to see the actual violations.