D — https://poolsuite.net | BeaverCheck Audit

Site Health

Score: 68 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

Page weighs 10.7 MB (4.9 MB transferred)

Performance › Page Weight Budget

3 image(s) missing alt attribute

Accessibility › Alt Text Quality

No <main> landmark found

Accessibility › Landmark Structure

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fpoolsuite.net)](https://beavercheck.com/results/d3221132-08bd-429f-89b0-09a09d0e1f30)

HTML

<a href="https://beavercheck.com/results/d3221132-08bd-429f-89b0-09a09d0e1f30"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpoolsuite.net" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fpoolsuite.net

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.49 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

16.43 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

989 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.001

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

8.62 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

18.06 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
connect.facebook.net/en_US/fbevents.js	1200.0 s	95.0 KiB
embed.radio.co/embed/sc9cb59935/song.js	60.0 s	53.7 KiB
/signals/config/1671765563059003?v=2.9.291&r=stable&domai...	1200.0 s	38.6 KiB
static.doubleclick.net/instream/ad_status.js	900.0 s	495 B
/tr/?id=1671765563059003&ev=PageView&dl=https%3A%2F%2Fpoo...	0.0 ms	19 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
div.h-full > div.flex-1 > div.youtube-only > div.youtube-loader `div.h-full > div.flex-1 > div.youtube-only > div.youtube-loader`	poolsuite.net/img/static.1c7d8655.gif	353.7 KiB	215.8 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:27.8 label:Time to first byte subpart:timeToFirstByte] map[duration:2416.285 label:Resource load delay subpart:resourceLoadDelay] map[duration:28.655 label:Resource load duration subpart:resourceLoadDuration] map[duration:29.152 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-DIV

nodeLabel: div.h-full > div.flex-1 > div.youtube-only > div.youtube-loader

path: 1,HTML,1,BODY,1,DIV,0,DIV,5,SECTION,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,2,DIV

selector: div.h-full > div.flex-1 > div.youtube-only > div.youtube-loader

snippet: <div data-v-50557430="" class="youtube-loader">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-DIV

nodeLabel: div.h-full > div.flex-1 > div.youtube-only > div.youtube-loader

path: 1,HTML,1,BODY,1,DIV,0,DIV,5,SECTION,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,2,DIV

selector: div.h-full > div.flex-1 > div.youtube-only > div.youtube-loader

snippet: <div data-v-50557430="" class="youtube-loader">

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.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-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.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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.

URL	Transfer Size	Duration
poolsuite.net/css/index.e3af5ecd.css	48.7 KiB	312 ms
poolsuite.net/css/chunk-vendors.12719797.css	3.8 KiB

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.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	15 ms

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

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.

Estimated savings: 0.0 ms 43.5 KiB

URL	Transfer Size	Est Savings
poolsuite.net/css/index.e3af5ecd.css	48.6 KiB	43.5 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 2.5 s 585.7 KiB

URL	Transfer Size	Est Savings
poolsuite.net/js/view-DefaultPage-vue.8f583e39.js	680.3 KiB	395.8 KiB
poolsuite.net/js/3099.f53a458d.js	119.8 KiB	49.9 KiB
poolsuite.net/js/chunk-vendors.e2d10250.js	93.0 KiB	48.5 KiB
connect.facebook.net/en_US/fbevents.js	94.8 KiB	32.3 KiB
embed.radio.co/embed/sc9cb59935/song.js	53.4 KiB	32.3 KiB
poolsuite.net/js/4098.0102c551.js	44.7 KiB	26.9 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
poolsuite.net/js/view-DefaultPage-vue.8f583e39.js	2.6 s	1.8 s	289 ms
Unattributable	867 ms	73 ms	0.0 ms
poolsuite.net/	302 ms	26 ms	2.8 ms
poolsuite.net/js/6488.f24db24b.js	259 ms	206 ms	6.3 ms
connect.facebook.net/en_US/fbevents.js	236 ms	182 ms	47 ms
poolsuite.net/js/3099.f53a458d.js	227 ms	162 ms	64 ms
poolsuite.net/js/4098.0102c551.js	197 ms	166 ms	31 ms
poolsuite.net/js/index.01134908.js	186 ms	181 ms	3.8 ms
embed.radio.co/embed/sc9cb59935/song.js	130 ms	82 ms	19 ms
/signals/config/1671765563059003?v=2.9.291&r=stable&domai...	122 ms	100 ms	21 ms
www.youtube.com/s/player/f4c47414/www-widgetapi.vflset/www-widgetapi.js	80 ms	64 ms	6.1 ms
poolsuite.net/js/6989.02f9b27d.js	75 ms	67 ms	7.1 ms
poolsuite.net/js/876.b157d96c.js	71 ms	69 ms	1.0 ms
poolsuite.net/js/chunk-vendors.e2d10250.js	51 ms	1.3 ms	38 ms

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

Category	Time Spent
Script Evaluation	3.3 s
Other	1.1 s
Script Parsing & Compilation	604 ms
Style & Layout	346 ms
Garbage Collection	126 ms
Rendering	79 ms
Parse HTML & CSS	42 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
poolsuite.net/js/view-DefaultPage-vue.8f583e39.js	681.3 KiB
www.youtube.com/s/player/f4c47414/player_embed_es6.vflset/en_US/base.js	431.3 KiB
poolsuite.net/img/background.f128a3af.jpg	429.4 KiB
poolsuite.net/vacation/4.jpg	414.8 KiB
poolsuite.net/vacation/1.jpg	383.5 KiB
poolsuite.net/img/static.1c7d8655.gif	354.0 KiB
poolsuite.net/vacation/3.jpg	242.5 KiB
/s/_/ytembeds/_/js/k=ytembeds.base.en_US.EkHW-yt-vuI.2021...	207.4 KiB
poolsuite.net/vacation/2.jpg	187.7 KiB
poolsuite.net/vacation/5.jpg	160.7 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
Get the app `header.h-8 > aside.h-full > a.button-component > img`
div.min-w-[372px] > div.h-full > button.button-component > img.w-[5px] `div.min-w-[372px] > div.h-full > button.button-component > img.w-[5px]`
div.min-w-[372px] > div.h-full > button.button-component > img.w-[5px] `div.min-w-[372px] > div.h-full > button.button-component > img.w-[5px]`

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 3 user timings

●Avoid long main-thread tasks 13 long tasks found

●Avoid non-composited animations 6 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 630 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 10 ms

●Avoid large layout shifts 8 layout shifts found

○INP breakdown

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.

Names and labels

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.

Failing Elements
div.flex > div.min-w-[372px] > div.h-full > button.button-component `div.flex > div.min-w-[372px] > div.h-full > button.button-component`
div.flex > div.min-w-[372px] > div.h-full > button.button-component `div.flex > div.min-w-[372px] > div.h-full > button.button-component`

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.

Failing Elements
div.min-w-[372px] > div.h-full > button.button-component > img.w-[5px] `div.min-w-[372px] > div.h-full > button.button-component > img.w-[5px]`
div.min-w-[372px] > div.h-full > button.button-component > img.w-[5px] `div.min-w-[372px] > div.h-full > button.button-component > img.w-[5px]`

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.

Best practices

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.

Failing Elements
Close icon `div.h-full > div#component-is-fm > div.drag-header > button.w-[18px]`
Toggle TV icon `div.h-full > div#component-is-fm > div.drag-header > button.w-[18px]`
Previous video icon `div.flex-1 > div.youtube-only > div.h-[17px] > button.bg-secondary`
Next video icon `div.flex-1 > div.youtube-only > div.h-[17px] > button.bg-secondary`
Toy Tonics `div.flex > div.flex-1 > h2.font-everyday > a.focus:outline-none`
Share icon `div.flex > div.flex > div.flex > button.disabled:opacity-20`
Favourite icon `div.flex > div.flex > div.flex > button.relative`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Image elements do not have `[alt]` attributes that are redundant text.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / Warning	Source
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 273, col 769

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
www.youtube.com/s/player/f4c47414/www-widgetapi.vflset/www-widgetapi.js line 210, col 99	`Uncaught (in promise) Error: Invalid video id`

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.

URL
poolsuite.net/js/view-DefaultPage-vue.8f583e39.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

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.

Content Best Practices

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.

Failing Elements
div.min-w-[372px] > div.h-full > button.button-component > img.w-[5px] `div.min-w-[372px] > div.h-full > button.button-component > img.w-[5px]`
div.min-w-[372px] > div.h-full > button.button-component > img.w-[5px] `div.min-w-[372px] > div.h-full > button.button-component > img.w-[5px]`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

394 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

3.22 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

71 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.020

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.65 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

3.29 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
connect.facebook.net/en_US/fbevents.js	1200.0 s	95.0 KiB
embed.radio.co/embed/sc9cb59935/song.js	60.0 s	53.8 KiB
/signals/config/1671765563059003?v=2.9.291&r=stable&domai...	1200.0 s	38.6 KiB
static.doubleclick.net/instream/ad_status.js	900.0 s	495 B
/tr/?id=1671765563059003&ev=PageView&dl=https%3A%2F%2Fpoo...	0.0 ms	19 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URL	Resource Size	Est Savings
poolsuite.net/img/static.1c7d8655.gif	353.7 KiB	215.8 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:30.733 label:Time to first byte subpart:timeToFirstByte] map[duration:2424.6 label:Resource load delay subpart:resourceLoadDelay] map[duration:24.689 label:Resource load duration subpart:resourceLoadDuration] map[duration:98.387 label:Element render delay subpart:elementRenderDelay]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

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.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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.

URL	Transfer Size	Duration
poolsuite.net/css/index.e3af5ecd.css	48.7 KiB	94 ms
poolsuite.net/css/chunk-vendors.12719797.css	3.8 KiB

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.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	10 ms

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

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.

Estimated savings: 30 ms 42.7 KiB

URL	Transfer Size	Est Savings
poolsuite.net/css/index.e3af5ecd.css	48.6 KiB	42.7 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 330 ms 586.6 KiB

URL	Transfer Size	Est Savings
poolsuite.net/js/view-DefaultPage-vue.8f583e39.js	680.3 KiB	396.3 KiB
poolsuite.net/js/3099.f53a458d.js	119.8 KiB	49.9 KiB
poolsuite.net/js/chunk-vendors.e2d10250.js	93.0 KiB	48.5 KiB
connect.facebook.net/en_US/fbevents.js	94.8 KiB	32.7 KiB
embed.radio.co/embed/sc9cb59935/song.js	53.4 KiB	32.3 KiB
poolsuite.net/js/4098.0102c551.js	44.7 KiB	26.9 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
poolsuite.net/js/view-DefaultPage-vue.8f583e39.js	681.4 KiB
www.youtube.com/s/player/f4c47414/player_embed_es6.vflset/en_US/base.js	431.3 KiB
poolsuite.net/img/background.f128a3af.jpg	429.4 KiB
poolsuite.net/vacation/4.jpg	414.8 KiB
poolsuite.net/vacation/1.jpg	383.4 KiB
poolsuite.net/img/static.1c7d8655.gif	354.0 KiB
poolsuite.net/vacation/3.jpg	242.5 KiB
/s/_/ytembeds/_/js/k=ytembeds.base.en_US.EkHW-yt-vuI.2021...	207.4 KiB
poolsuite.net/vacation/2.jpg	187.7 KiB
poolsuite.net/vacation/5.jpg	160.7 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 3 user timings

●JavaScript execution time 0.7 s

●Minimizes main-thread work 1.4 s

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 6 animated elements found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 430 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 10 ms

●Avoid large layout shifts 7 layout shifts found

○INP breakdown

Accessibility

Best practices

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.

Failing Elements
Close icon `div.h-full > div#component-is-fm > div.drag-header > button.w-[18px]`
Toggle TV icon `div.h-full > div#component-is-fm > div.drag-header > button.w-[18px]`
Contract icon `div.h-full > div#component-is-fm > div.drag-header > button.flex`
Previous video icon `div.flex-1 > div.youtube-only > div.h-[17px] > button.bg-secondary`
Next video icon `div.flex-1 > div.youtube-only > div.h-[17px] > button.bg-secondary`
UnbrokenOne `div.flex > div.flex-1 > h2.font-everyday > a.focus:outline-none`
Share icon `div.flex > div.flex > div.flex > button.disabled:opacity-20`
Favourite icon `div.flex > div.flex > div.flex > button.relative`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / Warning	Source
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 273, col 769

URL
poolsuite.net/js/view-DefaultPage-vue.8f583e39.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`

Results for https://poolsuite.net

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best practices

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

General

SEO

Keyboard Shortcuts