https://www.proantic.com/magazine/
Tested 2026-10-12 01:36:18 using Chrome 152.0.7977.64 (runtime settings)
This page is fast to paint, snappy to interact with and visually stable, but missing some accessibility basics, loose on best practices and weak on user privacy.
Visual metrics
Google Web Vitals
Accessibility · axe-core
The page ships 12 images (out of 12) 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.
The page has 6 font requests. Do you really need them? What value does the fonts give the user?
The page has 2 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.
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 | 366 ms | 366 ms | 366 ms | 366 ms | identical |
| Last visual change | 400 ms | 566 ms | 511 ms | 566 ms | runs disagree ±15% |
| Speed index | 373 ms | 394 ms | 391 ms | 405 ms | stable ±4% |
| Largest image | 400 ms | 566 ms | 511 ms | 566 ms | runs disagree ±15% |
| Largest contentful paint | 400 ms | 566 ms | 511 ms | 566 ms | runs disagree ±15% |
| Last meaningful paint | 400 ms | 566 ms | 511 ms | 566 ms | runs disagree ±15% |
| Visual readiness | 34 ms | 200 ms | 145 ms | 200 ms | runs disagree ±42% |
| Visual complete 85 | 400 ms | 433 ms | 466 ms | 566 ms | runs disagree ±19% |
| Visual complete 95 | 400 ms | 566 ms | 511 ms | 566 ms | runs disagree ±15% |
| Visual complete 99 | 400 ms | 566 ms | 511 ms | 566 ms | runs disagree ±15% |
Run 2 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 340 ms on a 198 ms first byte; the 2 render-blocking requests were done by 232 ms and the remaining ~108 ms is style and layout work (28 ms of it measured style recalculation).
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).
One large recalculation dominates. Restyling 559 elements cost 28 ms before the page painted (8.3 % of the time to First Contentful Paint), and a single recalculation of 544 elements accounts for 21 ms of it. Look for one class or inline-style change on a large container near the top of the DOM that restyles the whole subtree at once. The changes driving it are listed under Style invalidations below.
The recalculation work before first paint is 8.3 % of the time to First Contentful Paint.
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 | 195 ms | 14.6 KB | 193 ms |
20 ms | 10.4 KB | 20 ms | |
13 ms | 1.5 KB | 13 ms | |
scripts.min.jsblocks parser in body | 17 ms | 1.1 KB | 17 ms |
LCP resource | 154 ms | 183.6 KB | 154 ms |
184 ms · past LCP | 36.9 KB | 184 ms | |
218 ms · past LCP | 23.9 KB | 218 ms | |
16 ms | 5.5 KB | 16 ms | |
0107 ms214 msFCP 340 msFCP · LCP 428 ms |
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. 10 style recalculations and 2 112 layout invalidations fired after first paint, on a page the user was already looking at. The biggest driver is attribute style (2×). Start with the script under "Scripts causing invalidations" that keeps triggering it.
attribute: style2×attribute: rel1×Invalidations while the largest paint was still pending, so these delayed it.
| Reason | Style recalculations | Layout |
|---|---|---|
| A node was inserted into the page | 10 | – |
| A web font finished loadingPreload the font or use font-display so a late swap does not re-style the page. | – | 1 750 |
Churn on the fully rendered page: wasted work and possible jank, but no paint delay.
| Reason | Style recalculations | Layout |
|---|---|---|
| A web font finished loadingPreload the font or use font-display so a late swap does not re-style the page. | – | 362 |
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 | 7 | – |
| A stylesheet rule changed | 1 | – |
| A web font finished loadingPreload the font or use font-display so a late swap does not re-style the page. | – | 901 |
| An element entered layout | – | 918 |
| An element left layout | – | 3 |
| An element's size changed | – | 1 |
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.
modernImageFormatsThe page ships 12 images (out of 12) 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 6 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.
lazyLoadingImagesThe page has 2 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 1 CPU long task with the total of 64 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 64 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.
cacheHeadersThe page has 2 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 656 B 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.
decodingAsyncThe page has 2 images (out of 12) 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
avoidRenderBlockingThe page has 2 blocking requests and 1 in body parser blocking (1 JavaScript and 2 CSS).
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.
spofThe page has 1 request 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.
compressAssetsThe page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead.
In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith.
| URL | Transfer | Content |
|---|---|---|
| https://analytics.proantic.com/api/script.js | 33.5 KB | 33.2 KB |
privateAssetsThe 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.
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 8 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.
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.
thirdPartyThe page do 48% requests to third party domains (11 requests and 662 kB). First party is 12 requests and 127.2 kB. The page transfer more bytes from third party domains (662 kB) then first party (127.2 kB). The regex .*proantic.* was used to calculate first/third party requests.
Do not load most of your content from third party URLs.
unnecessaryHeadersThere are 17 responses that sets both a max-age and expires header. There are 23 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.
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
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
strictTransportSecurityHeaderSet a strict transport header to make sure the user always use HTTPS.
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.
thirdPartyPrivacyThe page has 48% requests that are 3rd party (11 requests with a size of 662 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 6 survelliance requests and uses 1 survelliance tool. The page do 6 surveillance requests and uses 1 surveillance tool. The page do 3 hosting requests and uses 1 hosting tool. The page do 2 analytics requests and uses 1 analytics 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.
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 2
0.0s0.3s0.4s0.5s0.6sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > div#page > div:eq(1) > div > div > div#site-content > div > div:eq(0) > main#content > div:eq(0) > div#inner-content > article#entry-18669 > div:eq(2) > a > img
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 94% of your 0.014 CLS. div#site-content moved at 546 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.
body > div#page > div:eq(1) > div > div > div#site-contentbody > div#page > div:eq(1) > div > div > header#masthead > div:eq(1)body > div#page > div:eq(1) > div > div > header#masthead > div:eq(0) > div > a > #textbody > div#page > div:eq(1) > div > div > header#masthead > div:eq(0) > p
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.
https://www.proantic.com/magazine/
| Header | Value |
|---|---|
cache-control | max-age=0, no-cache, s-maxage=10 |
content-encoding | gzip |
content-length | 14581 |
content-type | text/html; charset=UTF-8 |
date | Mon, 12 Oct 2026 01:36:39 GMT |
link | <https://www.proantic.com/magazine/wp-json/>; rel="https://api.w.org/", <https://wp.me/7EkP3>; rel=shortlink |
server | nginx |
vary | accept,content-type,Accept-Encoding |
x-content-type-options | nosniff |
x-frame-options | SAMEORIGIN |
x-mod-pagespeed | 1.13.35.2-0 |
Transfer size770.7 KB
Content size918.1 KB
Requests23
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 14.6 KB | 77.6 KB | 1 |
| css | 0 b | 14.2 KB | 83.1 KB | 3 |
| javascript | 0 b | 42.0 KB | 61.0 KB | 4 |
| image | 0 b | 567.1 KB | 564.7 KB | 5 |
| font | 0 b | 130.8 KB | 130.4 KB | 6 |
| favicon | 0 b | 1.4 KB | 1.1 KB | 1 |
| json | 0 b | 701 B | 287 B | 2 |
| other | 0 b | 0 b | 0 b | 1 |
| Total | 0 b | 770.7 KB | 918.1 KB | 23 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| www.proantic.com | 543 ms | 90.0 KB | 219.3 KB | 8 |
| fonts.googleapis.com | 41 ms | 2.3 KB | 21.3 KB | 1 |
| i0.wp.com | 803 ms | 530.5 KB | 528.5 KB | 3 |
| stats.wp.com | 114 ms | 1.7 KB | 3.7 KB | 1 |
| analytics.proantic.com | 162 ms | 34.2 KB | 33.5 KB | 4 |
| fonts.gstatic.com | 116 ms | 111.9 KB | 111.7 KB | 5 |
| pixel.wp.com | 85 ms | 177 B | 50 B | 1 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 4 weeks | 2 years |
| Last modified | 0 seconds | 17 weeks | 3 years |
Includes requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 0 b | 0 |
| font | 0 b | 0 |
| favicon | 1.4 KB | 1 |
| Total | 1.4 KB | 1 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 5.7 KB | 1 |
| image | 0 b | 0 |
| font | 0 b | 0 |
| favicon | 1.4 KB | 1 |
| other | 0 b | 1 |
| json | 222 B | 1 |
| Total | 7.3 KB | 4 |
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.
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.
All main-thread work during the full page load, not just the share that blocked input. Calculated from the Chrome trace.
parseHTMLstyleLayoutscriptParseCompilescriptEvaluationpaintCompositeRendergarbageCollectionotherMain-thread CPU time from the Chrome trace split by domain. First party is proantic.com.
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 category17
Transfer size770.7 KB
Content size918.1 KB
Requests23
Calculated using .*proantic.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 14.6 KB | 77.6 KB | 1 |
| css | 0 b | 11.9 KB | 61.8 KB | 2 |
| javascript | 0 b | 40.2 KB | 57.3 KB | 3 |
| image | 0 b | 36.4 KB | 36.1 KB | 1 |
| font | 0 b | 18.9 KB | 18.6 KB | 1 |
| favicon | 0 b | 1.4 KB | 1.1 KB | 1 |
| json | 0 b | 701 B | 287 B | 2 |
| other | 0 b | 0 b | 0 b | 1 |
| Total | N/A | 124.2 KB | 252.7 KB | 12 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 0 b | 0 b | 0 |
| css | 0 b | 2.3 KB | 21.3 KB | 1 |
| javascript | 0 b | 1.7 KB | 3.7 KB | 1 |
| image | 0 b | 530.6 KB | 528.6 KB | 4 |
| font | 0 b | 111.9 KB | 111.7 KB | 5 |
| favicon | 0 b | 0 b | 0 b | 0 |
| Total | N/A | 646.5 KB | 665.3 KB | 11 |
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.
