Download
Download
about:blank
[Link]
49 94 73 100
49
Performance
Values are estimated and may vary. The performance score is
calculated directly from these metrics. See calculator.
3.3 s 14.9 s
770 ms 0
Speed Index
3.9 s
INSIGHTS
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about
optimizing image size FCP LCP Unscored
Resource
URL
Size
[Link]-cover
about:blank 1/31
13/6/26, 12:08 a.m. about:blank
Resource
URL
Size
/photo-154…-5f7ceaf7f992?
[Link]-hover:scale-[1.04] 569.1 KiB
w=1600&q=80 ([Link])
[Link]-cover
/photo-150…-b723cf961d3e?
212.9 KiB
w=1600&q=80 ([Link])
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response,
and enabling text compression. FCP LCP Unscored
Avoids redirects
No compression applied
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the
download of unnecessary resources to improve page load. LCP Unscored
Initial Navigation
[Link] - 816 ms, 195.66 KiB
about:blank 2/31
13/6/26, 12:08 a.m. about:blank
…deps/svelte_events.js?v=d6f2b720 (localhost) - 1,754 ms, 0.98 KiB
about:blank 3/31
13/6/26, 12:08 a.m. about:blank
…runtime/[Link]?v=d6f2b720 (localhost) - 1,331 ms, 44.21 KiB
Preconnected origins
preconnect hints help the browser establish a connection earlier in the page load, saving time when the first
request for that origin is made. The following are the origins that the page preconnected to.
Preconnect candidates
Add preconnect hints to your most important origins, but try to use no more than 4.
[Link] 180 ms
[Link] 110 ms
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. FCP
LCP Unscored
[Link]?v=d6f2b720 10 KiB
…client/[Link]?v=d6f2b720 (localhost) --
[Link]?v=d6f2b720 0 KiB
…src/[Link]?v=d6f2b720 (localhost) --
about:blank 4/31
13/6/26, 12:08 a.m. about:blank
[Link]?v=d6f2b720 0 KiB
…state/[Link]?v=d6f2b720 (localhost) --
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM
will also increase memory usage. Learn how to avoid an excessive DOM size. Unscored
LCP breakdown
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources,
not within delays. LCP Unscored
Subpart Duration
[Link]-[1.1].[Link]:[Link]:text-6xl
3rd parties
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your
page's content. Unscored
gighmmpiobklfepjocnamgkkbiglidom 0 KiB 67 ms
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext-ad-filtering-
0 KiB 25 ms
solution/[Link]
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/[Link] 0 KiB 15 ms
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext-ad-filtering-
0 KiB 10 ms
solution/[Link]
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/[Link] 0 KiB 7 ms
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/[Link] 0 KiB 3 ms
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/[Link] 0 KiB 2 ms
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/[Link] 0 KiB 2 ms
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/[Link] 0 KiB 1 ms
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/adblock-uiscripts-
0 KiB 1 ms
rightclick_hook.js
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/[Link] 0 KiB 1 ms
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/ext/[Link] 0 KiB 0 ms
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/ext/[Link] 0 KiB 0 ms
kejbdjndbnbjgmefkgdddjlbokphdefk 0 KiB 9 ms
about:blank 5/31
13/6/26, 12:08 a.m. about:blank
chrome-extension://kejbdjndbnbjgmefkgdddjlbokphdefk/cs/ta/content_script_bin.js 0 KiB 5 ms
chrome-extension://kejbdjndbnbjgmefkgdddjlbokphdefk/cs/ta/tag_assistant_api_bin.js 0 KiB 4 ms
ghkcpcihdonjljjddkmjccibagkjohpi 0 KiB 4 ms
chrome-extension://ghkcpcihdonjljjddkmjccibagkjohpi/[Link] 0 KiB 4 ms
[Link] 0 KiB 1 ms
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
DIAGNOSTICS
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps
with this. Learn how to minimize main-thread work TBT Unscored
Other 2,702 ms
Rendering 96 ms
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript. FCP LCP
Unscored
about:blank 6/31
13/6/26, 12:08 a.m. about:blank
about:blank 7/31
13/6/26, 12:08 a.m. about:blank
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext-ad-
37.2 KiB 5.7 KiB
filtering-solution/[Link]
about:blank 8/31
13/6/26, 12:08 a.m. about:blank
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/cookie-banner-
10.0 KiB 5.3 KiB
[Link]
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Learn how to reduce unused JavaScript. FCP LCP Unscored
about:blank 9/31
13/6/26, 12:08 a.m. about:blank
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext-ad-
37.2 KiB 33.2 KiB
filtering-solution/[Link]
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext-ad-
37.9 KiB 20.1 KiB
filtering-solution/[Link]
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can
speed up these return navigations. Learn more about the bfcache Unscored
Pages with WebSocket cannot enter back/forward cache. Pending browser support
[Link]
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS. FCP LCP Unscored
Transfer Est
URL
Size Savings
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by
network activity. Learn how to reduce unused CSS. FCP LCP Unscored
Transfer Est
URL
Size Savings
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload
sizes. Unscored
about:blank 10/31
13/6/26, 12:08 a.m. about:blank
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long
main-thread tasks TBT Unscored
Unattributable 1,244 ms
Unattributable 2,796 ms 86 ms
Unattributable 2,714 ms 82 ms
Unattributable 3,325 ms 78 ms
Unattributable 2,640 ms 74 ms
[Link] 2,548 ms 92 ms
[Link] 2,477 ms 71 ms
[Link] 3,237 ms 63 ms
about:blank 11/31
13/6/26, 12:08 a.m. about:blank
More information about the performance of your application. These numbers don't directly affect the Performance score.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching. FCP LCP Unscored
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements
being added, removed, or their fonts changing as the page loads. CLS Unscored
Font display
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to
mitigate layout shifts with font metric overrides. Unscored
Forced reflow
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been
invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and
possible mitigations. Unscored
INP breakdown
Start investigating how to improve INP by looking at the longest subpart. Unscored
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading Unscored
Legacy JavaScript
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern
browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must
support older browsers. Learn why most sites can deploy ES6+ code without transpiling FCP LCP Unscored
Modern HTTP
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP. FCP
LCP Unscored
Render-blocking requests
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests
out of the critical path. FCP LCP Unscored
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile. Unscored
meta
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user
experiences. Learn more about User Timing marks. Unscored
about:blank 12/31
13/6/26, 12:08 a.m. about:blank
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps
with this. Learn how to reduce Javascript execution time. TBT Unscored
Total CPU
URL Script Evaluation Script Parse
Time
[Link] 1,341 ms 60 ms 2 ms
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animations CLS
Unscored
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image
dimensions CLS Unscored
94
Accessibility
These checks highlight opportunities to improve the accessibility of your
web app. Automatic detection can only detect a subset of issues and does
not guarantee the accessibility of your web app, so manual testing is also
encouraged.
CONTRAST
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
[Link]:text-slate-400
[Link]…
[Link]:text-slate-500
[Link]…
[Link]:text-slate-500
[Link]…
[Link]:text-slate-400
[Link]…
[Link]:text-slate-500
[Link]…
about:blank 13/31
13/6/26, 12:08 a.m. about:blank
Failing Elements
[Link]:text-slate-500
[Link]…
[Link]:text-slate-400
[Link]…
[Link]:text-slate-500
[Link]…
[Link]:text-slate-500
[Link]…
[Link]:text-slate-400
section#[Link]:bg-slate-900.s…
[Link]-slate…
[Link]-slate…
[Link]-slate…
[Link]-slate…
[Link]:text-slate-500
[Link]-all.d…
[Link]:text-slate-400
[Link]-all.d…
[Link]:text-slate-500
[Link]-all.d…
[Link]:text-slate-400
[Link]-all.d…
[Link]:text-slate-500
[Link]-all.d…
[Link]:text-slate-400
[Link]-all.d…
BEST PRACTICES
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Failing Elements
html
Links with the same destination should have the same description, to help users understand the link's purpose and decide
whether to follow it. Learn more about identical links. Unscored
Failing Elements
[Link]-s…
about:blank 14/31
13/6/26, 12:08 a.m. about:blank
Failing Elements
[Link]-s…
[Link]-s…
[Link]-s…
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text
adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more
about the alt attribute. Unscored
Failing Elements
[Link]-cover
[Link]-cover
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of
assistive technology, like a screen reader.
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls
focusable. Unscored
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive
elements. Learn how to decorate interactive elements with affordance hints. Unscored
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical
tab ordering. Unscored
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual
ordering. Unscored
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus
traps. Unscored
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new
content. Unscored
about:blank 15/31
13/6/26, 12:08 a.m. about:blank
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology.
Learn more about landmark elements. Unscored
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content. Unscored
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom
controls and labels. Unscored
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls. Unscored
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility
review.
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn
how to match ARIA attributes to their roles.
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>.
Learn how aria-hidden affects the document body.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values
for ARIA attributes.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA
attributes.
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who
rely on screen readers. Learn how to make buttons more accessible.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt
attribute. Learn more about the alt attribute.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less
than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of
a web page. Learn more about the viewport meta tag.
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA
attributes.
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available
to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
about:blank 16/31
13/6/26, 12:08 a.m. about:blank
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users
of assistive technologies. Learn more about prohibited ARIA roles.
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page
is relevant to their search. Learn more about document titles.
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user
chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not
announce the page's text correctly. Learn more about the lang attribute.
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the
navigation experience for screen reader users. Learn how to make links accessible.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more
about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly.
Learn more about proper list structure.
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating
experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the
targets. Learn more about touch targets.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate
and understand when using assistive technologies. Learn more about heading order.
Including a skip link can help users skip to the main content to save time. Learn more about skip links.
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more
about access keys. Unscored
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for
users who rely on screen readers. Learn how to make command elements more accessible. Unscored
about:blank 17/31
13/6/26, 12:08 a.m. about:blank
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Unscored
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these
elements. Learn how to make ARIA dialog elements more accessible. Unscored
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable
for users who rely on screen readers. Learn more about input field labels. Unscored
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it
unusable for users who rely on screen readers. Learn how to name meter elements. Unscored
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it
unusable for users who rely on screen readers. Learn how to label progressbar elements. Unscored
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles
and required attributes. Unscored
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about
roles and required children elements. Unscored
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions.
Learn more about ARIA roles and required parent element. Unscored
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA
roles. Unscored
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's
focusable descendents will not be announced. Learn more about the role=text attribute. Unscored
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable
for users who rely on screen readers. Learn more about toggle fields. Unscored
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it
unusable for users who rely on screen readers. Learn how to name tooltip elements. Unscored
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it
unusable for users who rely on screen readers. Learn more about labeling treeitem elements. Unscored
about:blank 18/31
13/6/26, 12:08 a.m. about:blank
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass
blocks. Unscored
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to
structure definition lists correctly. Unscored
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly
announce them. Learn how to structure definition lists correctly. Unscored
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn
how to fix duplicate ARIA IDs. Unscored
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either
the first, the last, or all of the labels. Learn how to use form labels. Unscored
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles. Unscored
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly.
Learn more about the lang attribute. Unscored
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input
button. Learn more about input buttons. Unscored
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the
purpose of the button. Learn about input image alt text. Unscored
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about
form element labels. Unscored
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for
users with low vision. Learn how to make links distinguishable. Unscored
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may
create a frustrating or confusing experience. Learn more about the refresh meta tag. Unscored
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey
meaning to users. Learn more about alt text for object elements. Unscored
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the
select element. Unscored
about:blank 19/31
13/6/26, 12:08 a.m. about:blank
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer
to other cells in the same table may improve the experience for screen reader users. Learn more about the headers
attribute. Unscored
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may
improve the experience for screen reader users. Learn more about table headers. Unscored
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how
to use the lang attribute. Unscored
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about
video captions. Unscored
The autocomplete attribute values must be valid and correctly applied for screen readers to function correctly. Learn more
about valid autocomplete values. Unscored
There are certain cases where the semantic role of an element with role="none" or role="presentation" does not
resolve to none or presentation. To ensure the element remains removed from the accessibility tree, you should not add any
global ARIA attributes to the element or make it focusable. Learn more about presentation role conflict. Unscored
Ensures SVG elements with an img, graphics-document or graphics-symbol role have an accessible text alternative. Learn
more about SVG alt text. Unscored
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table
mark-up helps users of screen readers. Learn more about summary and caption. Unscored
A heading with no content or inaccessible text prevent screen reader users from accessing information on the page's
structure. Learn more about headings. Unscored
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere
with the accessibility of the web page. Learn more about ARIA roles. Unscored
73
Best Practices
GENERAL
Third-party cookies may be blocked in some contexts. Learn more about preparing for third-party cookie restrictions.
about:blank 20/31
13/6/26, 12:08 a.m. about:blank
Name URL
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser
concerns. Learn more about this errors in console diagnostic audit
Source Description
about:blank 21/31
13/6/26, 12:08 a.m. about:blank
Source Description
0 01/data/query/production?
query=*%5B_type+%3D%3D+%22travelPackage%22%5D+%7C+order%28featured+desc%2C+_createdA
t+asc%29+%7B%0A%09%0A%09_id%2C%0A%09_createdAt%2C%0A%09title%2C%0A%09destination%2C%
0A%09price%2C%0A%09currency%2C%0A%09duration%2C%0A%09includes%2C%0A%09description%2C
%0A%09images%2C%0A%09featured%2C%0A%09popular%2C%0A%09departureDates%2C%0A%09spotsAv
about:blank 22/31
13/6/26, 12:08 a.m. about:blank
Source Description
/[Link]:0 (localhost) Failed to load resource: the server responded with a status of 404 (Not Found)
[Link]
…query/production?
query=…:1:0 (placehold Failed to load resource: net::ERR_FAILED
[Link])
…query/production?
query=…:1:0 (placehold Failed to load resource: net::ERR_FAILED
[Link])
…query/production?
query=…:1:0 (placehold Failed to load resource: net::ERR_FAILED
[Link])
…query/production?
query=…:1:0 (placehold Failed to load resource: net::ERR_FAILED
[Link])
…query/production?
query=…:1:0 (placehold Failed to load resource: net::ERR_FAILED
[Link])
…query/production?
query=…:1:0 (placehold Failed to load resource: net::ERR_FAILED
[Link])
…query/production?
query=…:1:0 (placehold Failed to load resource: net::ERR_FAILED
[Link])
…query/production?
query=…:1:0 (placehold Failed to load resource: net::ERR_FAILED
[Link])
…query/production?
query=…:1:0 (placehold Failed to load resource: net::ERR_FAILED
[Link])
…query/production?
query=…:1:0 (placehold Failed to load resource: net::ERR_FAILED
[Link])
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request
failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more
details on each issue.
Issue type
Cookie
/recaptcha/[Link]?render=TU_SITE_KEY_ACA ([Link])
about:blank 23/31
13/6/26, 12:08 a.m. about:blank
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a
CSP to prevent XSS Unscored
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks.
A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy. Unscored
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-
ups. Learn more about deploying the COOP header. Unscored
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header
control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from
embedding the page. Learn more about mitigating clickjacking. Unscored
Description Severity
The require-trusted-types-for directive in the Content-Security-Policy (CSP) header instructs user agents to
control the data passed to DOM XSS sink functions. Learn more about mitigating DOM-based XSS with Trusted Types.
Unscored
Description Severity
BROWSER COMPATIBILITY
Baseline Features
Lists web features used on the page and their Baseline status as of 2026-03-18. Learn more about Baseline. Unscored
about:blank 24/31
13/6/26, 12:08 a.m. about:blank
Unattributable
/[Link]:30
template Widely Available (2015-11-12)
(gighmmpiobklfepjocnamgkkbiglidom)
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content,
where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders
about:blank 25/31
13/6/26, 12:08 a.m. about:blank
from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite
for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password [Link] more
about user-friendly input fields.
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user
action instead. Learn more about the geolocation permission.
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to
user gestures instead. Learn more about responsibly getting permission for notifications.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how
to provide responsive images.
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the
Content-Type HTTP response header. Learn more about declaring the character encoding.
Source maps translate minified code to the original source code. This helps developers debug in production. In addition,
Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn
more about source maps. Unscored
Unattributable
chrome- chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/polyfill extension://gighmmpiobklfepjocnamgkkbiglidom/polyfill.
.js [Link]
chrome- chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/polyfill extension://gighmmpiobklfepjocnamgkkbiglidom/polyfill.
.js [Link]
chrome- chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/globals- extension://gighmmpiobklfepjocnamgkkbiglidom/globals-
[Link] [Link]
chrome- chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/cookie- extension://gighmmpiobklfepjocnamgkkbiglidom/cookie-
[Link] [Link]
about:blank 26/31
13/6/26, 12:08 a.m. about:blank
…routes/+[Link]?t=178… (localhost)
…routes/+[Link]?t=178… (localhost)
…routes/+[Link] (localhost)
…utils/[Link] (localhost)
…utils/[Link] (localhost)
…utils/[Link] (localhost)
…utils/[Link] (localhost)
…utils/[Link] (localhost)
…sanity/[Link] (localhost)
…sanity/[Link] (localhost)
…data/[Link] (localhost)
…config/[Link] (localhost)
…components/[Link] (localhost)
…components/[Link] (localhost)
…components/[Link] (localhost)
…components/[Link] (localhost)
…components/[Link] (localhost)
…components/[Link] (localhost)
…components/[Link]?t=178… (localhost)
…components/[Link] (localhost)
…components/[Link] (localhost)
…assets/[Link]?import (localhost)
…client/[Link] (localhost)
…esm-env/[Link]?v=d6f2b720 (localhost)
…esm-env/[Link]?v=d6f2b720 (localhost)
…esm-env/[Link]?v=d6f2b720 (localhost)
…src/[Link]?v=d6f2b720 (localhost)
…src/[Link]?v=d6f2b720 (localhost)
…src/[Link]?v=d6f2b720 (localhost)
…src/[Link]?v=d6f2b720 (localhost)
…src/[Link]?v=d6f2b720 (localhost)
…src/[Link]?v=d6f2b720 (localhost)
about:blank 27/31
13/6/26, 12:08 a.m. about:blank
…devalue/[Link]?v=d6f2b720 (localhost)
…utils/[Link]?v=d6f2b720 (localhost)
…utils/[Link]?v=d6f2b720 (localhost)
…utils/[Link]?v=d6f2b720 (localhost)
…utils/[Link]?v=d6f2b720 (localhost)
…utils/[Link]?v=d6f2b720 (localhost)
…utils/[Link]?v=d6f2b720 (localhost)
…utils/[Link]?v=d6f2b720 (localhost)
…runtime/[Link]?v=d6f2b720 (localhost)
…telemetry/[Link]?v=d6f2b720 (localhost)
…runtime/[Link]?v=d6f2b720 (localhost)
…runtime/[Link]?v=d6f2b720 (localhost)
…svelte-5/[Link]?v=d6f2b720 (localhost)
…client/[Link]?v=d6f2b720 (localhost)
…client/[Link]?v=d6f2b720 (localhost)
…client/[Link]?v=d6f2b720 (localhost)
…client/[Link]?v=d6f2b720 (localhost)
…client/[Link]?v=d6f2b720 (localhost)
…client/[Link]?v=d6f2b720 (localhost)
…client/[Link]?v=d6f2b720 (localhost)
…client/[Link]?v=d6f2b720 (localhost)
…client/[Link]?v=d6f2b720 (localhost)
…state/[Link]?v=d6f2b720 (localhost)
…state/[Link]?v=d6f2b720 (localhost)
…state/[Link]?v=d6f2b720 (localhost)
…internal/[Link]?v=d6f2b720 (localhost)
…paths/[Link]?v=d6f2b720 (localhost)
…paths/[Link]?v=d6f2b720 (localhost)
…env/[Link]?v=d6f2b720 (localhost)
…env/[Link]?v=d6f2b720 (localhost)
…internal/[Link]?v=d6f2b720 (localhost)
…internal/[Link]?v=d6f2b720 (localhost)
about:blank 28/31
13/6/26, 12:08 a.m. about:blank
…deps/[Link]?v=d6f2b720 (localhost)
…deps/svelte_legacy.js?v=d6f2b720 (localhost)
…deps/svelte_internal_flags_legacy.js?
…deps/svelte_internal_flags_legacy.[Link] (localhost)
v=d6f2b720 (localhost)
…deps/svelte_internal_disclose-[Link]?
…deps/svelte_internal_disclose-[Link] (localhost)
v=d6f2b720 (localhost)
…deps/svelte_internal_client.js?v=d6f2b720 (localhost)
…deps/svelte_events.js?v=d6f2b720 (localhost)
…deps/chunk-B-1-B7_t.js?v=d6f2b720 (localhost)
/@vite/client (localhost)
…static/public (localhost)
…client/[Link] (localhost)
…client/[Link] (localhost)
…generated/[Link] (localhost)
…generated/[Link] (localhost)
…nodes/[Link]?t=178… (localhost)
…nodes/[Link] (localhost)
…nodes/[Link]?t=178… (localhost)
…client/[Link] (localhost)
about:blank 29/31
13/6/26, 12:08 a.m. about:blank
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Unscored
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Unscored
100
SEO
These checks ensure that your page is following basic search engine
optimization advice. There are many additional factors Lighthouse does not
score here that may affect your search ranking, including performance on
Core Web Vitals. Learn more about Google Search Essentials.
Run the Structured Data Testing Tool to validate structured data. Learn more about Structured Data. Unscored
Run these additional validators on your site to check additional SEO best practices.
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more
about crawler directives.
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page
is relevant to their search. Learn more about document titles.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta
description.
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to
an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
[Link] is valid
If your [Link] file is malformed, crawlers may not be able to understand how you want your website to be crawled or
indexed. Learn more about [Link].
about:blank 30/31
13/6/26, 12:08 a.m. about:blank
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt
attribute. Learn more about the alt attribute.
hreflang links tell search engines what version of a page they should list in search results for a given language or region.
Learn more about hreflang.
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Captured at Jun 13, 2026, 12:07 Emulated Moto G Power with Single page session
AM GMT-3 Lighthouse 13.2.0
Initial page load Slow 4G throttling Using Chromium [Link] with
devtools
about:blank 31/31