84
Performance
Needs improvement
ViewMend
ViewMend resource check
AI-powered performance interpretation
Needs improvement
ViewMend report for selfyear.uk
ViewMend checked the page resources. Some lab metrics may be temporarily unavailable.
Check type
Resource
Data used
Resources and technical checks
Checked
May 20, 20:02
Devices
Mobile + Desktop
Actionable tasks
12
Resources found
6
Confidence
High 12 / Medium 0 / Review 0
Performance scores
Check results
Performance scores
The data below belongs to the selected device.
92
Accessibility
Good
79
Best Practices
Needs improvement
100
SEO
Good
59
Performance
Needs improvement
92
Accessibility
Good
78
Best Practices
Needs improvement
100
SEO
Good
Lab metrics
Core metrics
These are lab signals for the selected device. Below, ViewMend turns them into practical tasks.
FCP Needs improvement
2.6 s
Lab metric
LCP Needs improvement
3.4 s
Lab metric
TBT Needs improvement
229 ms
Lab metric
CLS Good
0.018
Lab metric
Speed Index Good
2.6 s
Lab metric
FCP Needs improvement
2.6 s
Lab metric
LCP Needs improvement
3.3 s
Lab metric
TBT Needs improvement
228 ms
Lab metric
CLS Good
0.006
Lab metric
Speed Index Good
2.6 s
Lab metric
ViewMend action plan
What to fix first
The first tasks below show concrete resources, changes, owners, and verification steps.
Main action
ViewMend found 6 practical tasks
On Mobile, start with delay third-party scripts.
- 7 tasks affect the first screen
- 4 CSS files can be reduced or checked for blocking
- 2 third-party JS scripts can be delayed
- 4 JavaScript files can be reduced or delayed
- 2 images need optimization
- Potential savings: 860 KB
1
Delay third-party scripts
8 third-party script can add network waiting and main-thread work.
What found
ViewMend found several vendor scripts. Review them as one task so duplicate tags and late-loading rules are handled together.
What to do
- Confirm the vendor script is required on this page.
- Move it after the first screen or after user consent/interaction.
- Load it with async/defer when it does not block core rendering.
- Remove duplicate tags from tag manager or templates.
Expected effect
Can reduce main-thread blocking and improve TBT by moving non-critical vendor work later.
Who
Frontend developer
Affected resources
Showing 3 of 8
www.googletagmanager.com / js
www.googletagmanager.com/gtag/js
www.googletagmanager.com / js
www.googletagmanager.com/gtag/js
www.googletagmanager.com / js
www.googletagmanager.com/gtag/js
18132118690
googleads.g.doubleclick.net/pagead/viewthroughconversion/18132118690
collect
www.google.com/ccm/collect
18132118690
googleads.g.doubleclick.net/pagead/viewthroughconversion/18132118690
www.googletagmanager.com / js
www.googletagmanager.com/gtag/js
18132118690
googleads.g.doubleclick.net/pagead/viewthroughconversion/18132118690
How to verify after the fix
Rerun ViewMend audit and compare the affected metric.
Asking ViewMend AI...
Plain explanation
How to fix
How to verify
Problem
Affected resources
Required actions
What not to do / risks
Acceptance criteria
Verification steps
Create an account to save this task
2
Review third-party requests
2 third-party request can add network waiting or vendor cost.
What found
ViewMend found third-party requests. Review whether they are needed during initial load and whether they can be delayed.
What to do
- Check whether this request is needed during initial load.
- Cache versioned static assets for longer.
- Compress text resources with Brotli or gzip.
- Delay third-party or non-critical requests until after first content.
Expected effect
Can reduce vendor waiting time and improve performance when non-critical third-party requests move later.
Who
Developer / hosting
Affected resources
2 resources
favicon.ico
selfyear.uk/favicon.ico
site.webmanifest
selfyear.uk/site.webmanifest
How to verify after the fix
Rerun ViewMend audit and compare the affected metric.
Asking ViewMend AI...
Plain explanation
How to fix
How to verify
Problem
Affected resources
Required actions
What not to do / risks
Acceptance criteria
Verification steps
Create an account to save this task
3
Optimize web font loading
3 font resource can delay text rendering or the first screen.
What found
ViewMend found font resources. Review the font families, weights, connection hints, and loading priority together.
What to do
- Keep only the font families, weights, and styles used on this page.
- Add preconnect for fonts.googleapis.com and fonts.gstatic.com.
- Confirm font-display: swap is used for the loaded fonts.
- If the font is critical for the first screen, consider preload for the critical font file.
- If possible, replace it with a system font or self-host the font files.
Expected effect
Can make text appear sooner and improve FCP / LCP when font loading is less blocking.
Who
Frontend developer
Affected resources
3 resources
fonts.googleapis.com / css2
fonts.googleapis.com/css2
UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa1ZL7W0Q5nw.woff2
fonts.gstatic.com/s/inter/v20/UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa1ZL7W0Q5nw.woff2
fonts.googleapis.com / css2
fonts.googleapis.com/css2
How to verify after the fix
Rerun ViewMend audit and compare the affected metric.
Asking ViewMend AI...
Plain explanation
How to fix
How to verify
Problem
Affected resources
Required actions
What not to do / risks
Acceptance criteria
Verification steps
Create an account to save this task
4
Reduce JavaScript files
2 JavaScript file can add download, parse, or execution cost.
What found
ViewMend found multiple JavaScript resources with optimization work. Treat them as one bundle and loading strategy task.
What to do
- Open the affected URL or selector.
- Apply the recommendation that matches this resource.
- Rerun ViewMend and compare the affected metric.
Expected effect
May reduce download, parse, and execution work, which helps TBT and page responsiveness.
Who
Developer
Affected resources
2 resources
selfyear.uk
https://selfyear.uk
public-CPYCXqvs.js
selfyear.uk/build/assets/public-CPYCXqvs.js
How to verify after the fix
Rerun ViewMend audit and compare the affected metric.
Asking ViewMend AI...
Plain explanation
How to fix
How to verify
Problem
Affected resources
Required actions
What not to do / risks
Acceptance criteria
Verification steps
Create an account to save this task
5
Review this affected resource
section.hero > div.container > div.hero-content > p.hero-text needs a targeted technical review.
What found
ViewMend found a concrete resource for this task. Use the URL below as the starting point for the fix.
What to do
- Open the affected URL or selector.
- Apply the recommendation that matches this resource.
- Rerun ViewMend and compare the affected metric.
Expected effect
Can improve after the affected resource is fixed and retested.
Who
Developer
section.hero > div.container > div.hero-content > p.hero-text
section.hero > div.container > div.hero-content > p.hero-text
How to verify after the fix
Rerun ViewMend audit and compare the affected metric.
Asking ViewMend AI...
Plain explanation
How to fix
How to verify
Problem
Affected resources
Required actions
What not to do / risks
Acceptance criteria
Verification steps
Create an account to save this task
6
Optimize web font loading
fonts.googleapis.com / css2 can delay text rendering and the first visible screen.
What found
ViewMend found a web font stylesheet from fonts.googleapis.com. It can sit in the first-screen path because the browser must discover the font CSS and then fetch font files.
What to do
- Keep only the font families, weights, and styles used on this page.
- Add preconnect for fonts.googleapis.com and fonts.gstatic.com.
- Confirm font-display: swap is used for the loaded fonts.
- If the font is critical for the first screen, consider preload for the critical font file.
- If possible, replace it with a system font or self-host the font files.
Expected effect
Can make text appear sooner and improve FCP / LCP when fonts are in the first-screen path.
Who
Frontend developer
fonts.googleapis.com / css2
https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&display=swap
How to verify after the fix
Rerun ViewMend audit and compare the affected metric.
Asking ViewMend AI...
Plain explanation
How to fix
How to verify
Problem
Affected resources
Required actions
What not to do / risks
Acceptance criteria
Verification steps
Create an account to save this task
Symptoms
LCP: 3.3 s
FCP: 2.6 s
Speed Index: 2.6 s
TBT: 228 ms
CLS: 0.006
1
Review third-party requests
2 third-party request can add network waiting or vendor cost.
What found
ViewMend found third-party requests. Review whether they are needed during initial load and whether they can be delayed.
What to do
- Check whether this request is needed during initial load.
- Cache versioned static assets for longer.
- Compress text resources with Brotli or gzip.
- Delay third-party or non-critical requests until after first content.
Expected effect
Can reduce vendor waiting time and improve LCP / FCP / Speed Index when non-critical third-party requests move later.
Who
Developer / hosting
Affected resources
2 resources
favicon.ico
selfyear.uk/favicon.ico
site.webmanifest
selfyear.uk/site.webmanifest
How to verify after the fix
Rerun ViewMend audit and compare the affected metric.
Asking ViewMend AI...
Plain explanation
How to fix
How to verify
Problem
Affected resources
Required actions
What not to do / risks
Acceptance criteria
Verification steps
Create an account to save this task
2
Delay third-party scripts
4 third-party script can add network waiting and main-thread work.
What found
ViewMend found several vendor scripts. Review them as one task so duplicate tags and late-loading rules are handled together.
What to do
- Confirm the vendor script is required on this page.
- Move it after the first screen or after user consent/interaction.
- Load it with async/defer when it does not block core rendering.
- Remove duplicate tags from tag manager or templates.
Expected effect
Can reduce main-thread blocking and improve Speed Index / TBT by moving non-critical vendor work later.
Who
Frontend developer
Affected resources
Showing 3 of 4
www.googletagmanager.com / js
www.googletagmanager.com/gtag/js
www.googletagmanager.com / js
www.googletagmanager.com/gtag/js
18132118690
googleads.g.doubleclick.net/pagead/viewthroughconversion/18132118690
collect
www.google.com/ccm/collect
How to verify after the fix
Rerun ViewMend audit and compare the affected metric.
Asking ViewMend AI...
Plain explanation
How to fix
How to verify
Problem
Affected resources
Required actions
What not to do / risks
Acceptance criteria
Verification steps
Create an account to save this task
3
Reduce JavaScript files
2 JavaScript file can add download, parse, or execution cost.
What found
ViewMend found multiple JavaScript resources with optimization work. Treat them as one bundle and loading strategy task.
What to do
- Open the affected URL or selector.
- Apply the recommendation that matches this resource.
- Rerun ViewMend and compare the affected metric.
Expected effect
May reduce download, parse, and execution work, which helps TBT and page responsiveness.
Who
Developer
Affected resources
2 resources
selfyear.uk
https://selfyear.uk
public-CPYCXqvs.js
selfyear.uk/build/assets/public-CPYCXqvs.js
How to verify after the fix
Rerun ViewMend audit and compare the affected metric.
Asking ViewMend AI...
Plain explanation
How to fix
How to verify
Problem
Affected resources
Required actions
What not to do / risks
Acceptance criteria
Verification steps
Create an account to save this task
4
Optimize web font loading
2 font resource can delay text rendering or the first screen.
What found
ViewMend found font resources. Review the font families, weights, connection hints, and loading priority together.
What to do
- Keep only the font families, weights, and styles used on this page.
- Add preconnect for fonts.googleapis.com and fonts.gstatic.com.
- Confirm font-display: swap is used for the loaded fonts.
- If the font is critical for the first screen, consider preload for the critical font file.
- If possible, replace it with a system font or self-host the font files.
Expected effect
Can make text appear sooner and improve LCP / FCP / Speed Index when font loading is less blocking.
Who
Frontend developer
Affected resources
2 resources
fonts.googleapis.com / css2
fonts.googleapis.com/css2
UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa1ZL7W0Q5nw.woff2
fonts.gstatic.com/s/inter/v20/UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa1ZL7W0Q5nw.woff2
How to verify after the fix
Rerun ViewMend audit and compare the affected metric.
Asking ViewMend AI...
Plain explanation
How to fix
How to verify
Problem
Affected resources
Required actions
What not to do / risks
Acceptance criteria
Verification steps
Create an account to save this task
5
Review this affected resource
section.hero > div.container > div.hero-content > h1 needs a targeted technical review.
What found
ViewMend found a concrete resource for this task. Use the URL below as the starting point for the fix.
What to do
- Open the affected URL or selector.
- Apply the recommendation that matches this resource.
- Rerun ViewMend and compare the affected metric.
Expected effect
Can improve LCP / FCP after the affected resource is fixed and retested.
Who
Developer
section.hero > div.container > div.hero-content > h1
section.hero > div.container > div.hero-content > h1
How to verify after the fix
Rerun ViewMend audit and compare the affected metric.
Asking ViewMend AI...
Plain explanation
How to fix
How to verify
Problem
Affected resources
Required actions
What not to do / risks
Acceptance criteria
Verification steps
Create an account to save this task
6
Optimize web font loading
fonts.googleapis.com / css2 can delay text rendering and the first visible screen.
What found
ViewMend found a web font stylesheet from fonts.googleapis.com. It can sit in the first-screen path because the browser must discover the font CSS and then fetch font files.
What to do
- Keep only the font families, weights, and styles used on this page.
- Add preconnect for fonts.googleapis.com and fonts.gstatic.com.
- Confirm font-display: swap is used for the loaded fonts.
- If the font is critical for the first screen, consider preload for the critical font file.
- If possible, replace it with a system font or self-host the font files.
Expected effect
Can make text appear sooner and improve LCP / FCP when fonts are in the first-screen path.
Who
Frontend developer
fonts.googleapis.com / css2
https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&display=swap
How to verify after the fix
Rerun ViewMend audit and compare the affected metric.
Asking ViewMend AI...
Plain explanation
How to fix
How to verify
Problem
Affected resources
Required actions
What not to do / risks
Acceptance criteria
Verification steps
Create an account to save this task
Page map
Resources, services, and technical signals found by ViewMend.
Third-party resources
Domains used by the page to load scripts, images, fonts, styles, or other files.
- fonts.googleapis.com
- 1 resource stylesheet
- googletagmanager.com
- 1 resource script
- fonts.gstatic.com
- 1 resource font
- googleads.g.doubleclick.net
- 1 resource script
- google.com
- 1 resource image
Page links
Internal, external, anchor, and utility links found in the page HTML.
- Internal links
- 43
Images
2 images found
- Total images
- 2
JavaScript
4 scripts found
- JavaScript files
- 4
- Third-party scripts
- 3
- Without async/defer
- 1
- Large scripts
- 1
- Total size
- 163 KB
CSS and fonts
Stylesheets and font resources detected on the page.
- CSS files
- 2
- Font stylesheets
- 1
- Font files
- 1
- Font domains
- fonts.gstatic.com
SEO / HTML basics
Basic HTML signals collected by ViewMend.
- Title
- Found
- Meta description
- Found
- Canonical
- https://selfyear.uk/
- H1 count
- 1
- Lang
- en
Server and indexing
Server response, indexing, and delivery signals.
- Status code
- 200
- Final URL
- https://selfyear.uk/
- noindex
- No
- nofollow
- No
- Cache-Control
- no-cache, private
ViewMend AI
AI Fix Plan
AI uses the available ViewMend check data. Some lab metrics may be unavailable.
Ask AI Developer task Ask about one issue 1 credit Developer task Generate AI Fix Plan Uses 5 AI credits Generating... Generated AI Fix Plan fixPlanAnswer ? 'Generated AI Fix Plan' : 'Generate AI Fix Plan'
5 credits
Generate an AI Fix Plan for this report
AI uses the available ViewMend check data. Some lab metrics may be unavailable.
AI credits are only used when you request AI output.
Short summary
Biggest likely win
Best first fix
Can wait
Open full AI Fix Plan
Fix first
Can wait
- -
Recommended order
How to retest
Developer summary
Visual evidence
Visual loading
Check what users see while the first screen is loading.
Mobile
Screenshot unavailable for this check.
Filmstrip
8 framesSlowest frames are shown first.
Desktop
Screenshot unavailable for this check.
Filmstrip
8 framesSlowest frames are shown first.
Passed checks
Passed checks
74 checks passed
73 checks passed
ViewMend also checked technical signals that do not require action.
Passed checks
Passed checks list
74 checks passed 73 checks passedSecurity
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 in...
Avoids requesting the geolocation permission on page load
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 per...
Avoids requesting the notification permission on page load
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...
HTML / Page basics
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
A `` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
`<html>` element has a `[lang]` attribute
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 is...
`<html>` element has a valid value for its `[lang]` attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the `lang` 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.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a `` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declari...
Avoids an excessive DOM size
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
247 elements
Optimize DOM size
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 ex...
Optimize viewport for mobile
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
Performance
Cumulative Layout Shift
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
0.018
Initial server response time was short
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Root document took 60 ms
Minimizes main-thread work
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
1.0 s
JavaScript execution time
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.
0.4 s
Speed Index
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
2.6 s
Images
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Image elements have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
JavaScript
`<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.
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.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Duplicated JavaScript
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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...
CSS / Fonts
All text remains visible during webfont loads
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legi...
99.8% legible text
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.
Network
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Avoids enormous network payloads
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Total size was 485 KiB
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more about HTTP/2.
Page didn't prevent back/forward cache restoration
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 bfc...
SEO
Links are crawlable
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 s...
Page isn’t blocked from indexing
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.
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Document has a valid `hreflang`
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`.
Document has a valid `rel=canonical`
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Accessibility
`[aria-*]` attributes match their roles
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.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
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...
`[aria-hidden="true"]` is not present on the document `<body>`
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document ``. Learn how `aria-hidden` affects the document body.
`[aria-hidden="true"]` elements do not contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn...
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
`[role]` values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
`[aria-*]` attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
`[aria-*]` attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
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 acces...
Heading elements appear in a sequentially-descending order
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 mo...
Links have a discernible name
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 ma...
Best Practices
No browser errors logged to the console
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 diagnosti...
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Page has valid source maps
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 de...
Other checks
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.
Definition list items are wrapped in `<dl>` elements
Definition list items (`` and ``) must be wrapped in a parent `` element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly...
Document has a `<title>` element
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 documen...
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Screen readers require list items (``) to be contained within a parent ``, `` or `` to be announced properly. Learn more about proper list structure.
Touch targets have sufficient size and spacing.
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.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Lea...
Avoids `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Modern HTTP
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
Security
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 in...
Avoids requesting the geolocation permission on page load
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 per...
Avoids requesting the notification permission on page load
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...
HTML / Page basics
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
A `` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
`<html>` element has a `[lang]` attribute
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 is...
`<html>` element has a valid value for its `[lang]` attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the `lang` 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.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a `` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declari...
Avoids an excessive DOM size
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
247 elements
Optimize DOM size
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 ex...
Optimize viewport for mobile
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
Performance
Cumulative Layout Shift
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
0.006
Initial server response time was short
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Root document took 50 ms
Minimizes main-thread work
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
1.0 s
JavaScript execution time
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.
0.4 s
Images
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Image elements have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
JavaScript
`<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.
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.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Duplicated JavaScript
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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...
CSS / Fonts
All text remains visible during webfont loads
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
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.
Network
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Avoids enormous network payloads
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Total size was 485 KiB
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more about HTTP/2.
Page didn't prevent back/forward cache restoration
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 bfc...
SEO
Links are crawlable
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 s...
Page isn’t blocked from indexing
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.
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Document has a valid `hreflang`
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`.
Document has a valid `rel=canonical`
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Accessibility
`[aria-*]` attributes match their roles
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.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
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...
`[aria-hidden="true"]` is not present on the document `<body>`
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document ``. Learn how `aria-hidden` affects the document body.
`[aria-hidden="true"]` elements do not contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn...
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
`[role]` values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
`[aria-*]` attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
`[aria-*]` attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
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 acces...
Heading elements appear in a sequentially-descending order
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 mo...
Links have a discernible name
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 ma...
Best Practices
No browser errors logged to the console
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 diagnosti...
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Page has valid source maps
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 de...
Other checks
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.
Definition list items are wrapped in `<dl>` elements
Definition list items (`` and ``) must be wrapped in a parent `` element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly...
Document has a `<title>` element
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 documen...
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Screen readers require list items (``) to be contained within a parent ``, `` or `` to be announced properly. Learn more about proper list structure.
Touch targets have sufficient size and spacing.
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.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Lea...
Avoids `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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 p...
Modern HTTP
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
Screenshot preview