kh4leoni.github.io

When JavaScript takes a long time to execute it can slow down website performance.

A large model can slow down a website by increasing the memory required and time taken to calculate and display changes.

This measures how long it takes a browser to render the first piece of content when someone visits a website.

This measures how long it takes a page to become fully interactive.

This approximates when the main content of the page is visible to users.

Lazily loading above the fold images can negatively affect performance.

When the main thread is busy the website may not respond quickly to user interactions.

This measures the time from when a user first interacts with a website to the time when the browser is actually able to respond to that interaction.

null

A high latency is an indication that the backend server is overloaded or performing poorly.

External scripts dynamically injected via document.write() can delay page load by tens of seconds.

Preload optional fonts so that first-time visitors can use them and to prevent layout shifting.

Delivering critical JavaScript and CSS inline and deferring all non-critical JavaScript and CSS can help prevent render blocking.

Server response times can be improved by optimizing server-side code or upgrading server hardware.

This indicates how quickly the contents of a page are visibly populated.

Some third-party embeds can be lazy loaded and replaced with a facade until they are required.

This measures the total amount of time that a page is blocked from responding to user input, such as mouse clicks, screen taps, or keyboard presses.

Excessively large page sizes can lead to long load times for visitors.

Preloading of key resources can make your pages load faster.

Incorrect character encoding can result in garbled text and is properly declared in the charset attribute or the Content-Type HTTP response header.

Low-contrast text can be difficult or even impossible for many visitors to read.

This measures unexpected page movements which visitors find annoying and can intefere with website functionality.

Specifying a doctype prevents the browser from switching to quirks mode, which can cause a website to render in unexpected ways.

Ensure text is user-visible and avoid flashes of invisible text while webfonts are loading.

Smaller font sizes can be difficult to read especially on mobile devices.

Users are mistrustful or confused by websites that request their location without context.

Images displayed with an incorrect aspect ratio look distorted.

Images should be responsive and proportional to the display size and the pixel ratio to maximize image clarity.

Users do not expect a page to refresh automatically as such refreshing can be disorienting.

Unload event listeners do not fire reliably and listening for them can intefere with website functionality and browser optimizations.

Users are mistrustful of or confused by sites that request to send notifications without context.

Interactive elements like buttons and links should be large enough and have enough space around them to be easy to tap without overlapping onto other elements.

Images should have an explicit width and height to reduce layout shifts.

Touch and wheel event listeners should be marked as passive to improve scroll performance.

Correctly setting the viewport optimizes websites for mobile screen sizes and also prevents delays to user input.

Deprecated APIs are scheduled to be removed from browsers and can introduce errors and vulnerabilities.

Console errors indicate unresolved problems that can lead to security issues.

Inspector issues indicate unresolved problems which can include security issues.

All websites should be protected with HTTPS including ones that don't handle sensitive data.

Some third-party JavaScript libraries contain known security vulnerabilities that are easily identified and exploited by attackers.

Preventing password fields from being pasted into undermines good security policy.

Access keys let users quickly focus on or navigate to a part of the page and must be unique.

When definition lists are not properly marked up screen readers may produce confusing or inaccurate output.

Definition list items must be wrapped in a parent element to ensure that screen readers can properly announce them.

All focusable elements must have a unique id to ensure that they're visible to assistive technologies.

The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies.

Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers.

Screen reader users rely on frame titles to describe the contents of frames.

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.

If the website doesn't specify a language correctly screen readers might not be able to read the text correctly.

Specifying a valid land attribute helps screen readers announce text correctly.

When an image is being used as a button providing alternative text can help screen reader users understand the purpose of the button.

Labels ensure that forms are announced properly by assistive technologies like screen readers.

Link text that is discernible, unique, and focusable improves the navigation experience for screen reader users.

Lists must only contain list elements so that screen readers can correctly announce lists.

List items must be contained within a parent list for screen readers to properly announce lists.

Disabling zooming and scaling is problematic for users with low vision who rely on screen magnification to properly see the contents of a website.

Screen readers cannot translate non-text such as objects so alternate text should be provided for these elements. `\u003cobject\u003e` elements helps screen readers convey meaning to users.

A tabindex value greater than 0 implies an explicit navigation ordering which often creates frustrating experiences for users who rely on assistive technologies.

Screen readers have a specific way of announcing tables and when tables are not properly marked up, this creates the opportunity for confusing or inaccurate screen reader output.

When tables are not marked up semantically and do not have the correct header structure, screen reader users cannot correctly perceive the relationships between the cells and their contents visually.

Specifying a valid lang attributes ensure that text is pronounced correctly by a screen reader.

When a video provides a caption it is easier for deaf and hearing impaired users to access its information.

Valid canonical links tell search engines which version of a page to crawl and display to users in search results.

Search engines use correctly formatted links to crawl websites.

Search engine users rely on the document title to determine if a page is relevant to their search.

Many sites provide different versions of a page based on a user's language or region and hreflang links tell search engines the URLs for all the versions of a page so that they can display the correct version.

Pages with unsuccessful HTTP status codes may not be indexed by search engines properly.

Images should have a descriptive alternate text which is meaningful for search engines and users.

Search engines are unable to include websites in search results if they don't have permission to crawl them.

Descriptive link text helps search engines understand your content.

Meta descriptions may be included in search results to help convey website content.

Search engines can't index plugin content and many devices restrict plugins or don't support them.

A valid robots.txt is required for search engines to understand how to crawl or index a website.

Search engines use structured data to understand what kind of content is on a website.