Hollysonders.com Site Title
Holly Sonders
Hollysonders.com Test Results
Hollysonders.com Mobile Performance: 0/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript. Potential savings of 252 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Preload key requests. Potential savings of 1,080 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Serve images in next-gen formats. Potential savings of 65 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Efficiently encode images. Potential savings of 28 KiB
Optimized images load faster and consume less cellular data. Learn more.
Eliminate render-blocking resources. 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Remove unused CSS. 0 ms
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Budgets
Performance budgets set standards for the performance of your site.
Timing budget
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Serve static assets with an efficient cache policy
15 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
3.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
1.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
15 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Keep request counts low and transfer sizes small
36 requests • 1,090 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid long main-thread tasks
11 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoids an excessive DOM size
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
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.
Hollysonders.com Mobile SEO: 0/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
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.
Image elements have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
Document doesn't use 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. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Tap targets are sized appropriately
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
1 error found
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.
Hollysonders.com Mobile Best Practices: 0/100
Quick overview:
User Experience
Fonts with `font-display: optional` are preloaded
Preload `optional` fonts so first-time visitors may use them. Learn More
Browser Compatibility
Charset declaration is missing or occurs too late in the HTML
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.
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more. Document must contain a doctype
General
Missing source maps for large first-party JavaScript
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.
Browser errors were 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
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Does not use HTTPS
1 insecure request found
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 servedover HTTPS. HTTPS prevents intruders 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.
Hollysonders.com Mobile Progressive Web App: 39/100
Quick overview:
PWA Optimized
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Does not use HTTPS
1 insecure request found
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 servedover HTTPS. HTTPS prevents intruders 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.
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Hollysonders.com Mobile Accessibility: 0/100
Quick overview:
Navigation
These are opportunities to improve keyboard navigation in your application.
No element has a `[tabindex]` value greater than 0
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.
`[id]` attributes on active, focusable elements are unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
`[accesskey]` values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
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 more.
Audio and video
These are opportunities to provide alternative content for audio and video. This may improve the experience for users with hearing or vision impairments.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Audio descriptions provide relevant information for videos that dialogue cannot, such as facial expressions and scenes. Learn more.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
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.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
`<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 more.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
A table being used for layout purposes should not include data elements, such as the th or caption elements or the summary attribute, because this can create a confusing experience for screen reader users. Learn more.
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.
Definition list items are wrapped in `<dl>` elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.
`<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.
Names and labels
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.
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.
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 more.
Image elements have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
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 more.
`<object>` elements have `[alt]` text
Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey meaning to users. Learn more.
No form fields have multiple labels
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 more.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
`<input type="image">` elements have `[alt]` text
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 more.
`<frame>` or `<iframe>` elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[role]`s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.
ARIA toggle fields have accessible names
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.
ARIA input fields have accessible names
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.
`[aria-*]` attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
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.
`[aria-*]` attributes match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
`[role]` values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
`[aria-*]` attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
`[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 more.
`[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 `<body>`. Learn more.
`[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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element has a valid value for its `[lang]` attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
`[lang]` attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.
`<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 isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
Best practices
These items highlight common accessibility best practices.
`[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.
The document does not use `<meta http-equiv="refresh">`
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.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar tests
www.hollysonders.com
www.hollysonders.net
www.hollysonders.org
www.hollysonders.info
www.hollysonders.biz
www.hollysonders.us
www.hollysonders.mobi
www.ollysonders.com
www.hollysonders.com
www.bollysonders.com
www.hbollysonders.com
www.bhollysonders.com
www.gollysonders.com
www.hgollysonders.com
www.ghollysonders.com
www.yollysonders.com
www.hyollysonders.com
www.yhollysonders.com
www.uollysonders.com
www.huollysonders.com
www.uhollysonders.com
www.jollysonders.com
www.hjollysonders.com
www.jhollysonders.com
www.nollysonders.com
www.hnollysonders.com
www.nhollysonders.com
www.hllysonders.com
www.hillysonders.com
www.hoillysonders.com
www.hiollysonders.com
www.hkllysonders.com
www.hokllysonders.com
www.hkollysonders.com
www.hlllysonders.com
www.holllysonders.com
www.hlollysonders.com
www.hpllysonders.com
www.hopllysonders.com
www.hpollysonders.com
www.holysonders.com
www.hoplysonders.com
www.holplysonders.com
www.hoolysonders.com
www.hololysonders.com
www.hoollysonders.com
www.hoklysonders.com
www.holklysonders.com
www.holpysonders.com
www.hollpysonders.com
www.holoysonders.com
www.holloysonders.com
www.holkysonders.com
www.hollkysonders.com
www.hollsonders.com
www.holltsonders.com
www.hollytsonders.com
www.holltysonders.com
www.hollgsonders.com
www.hollygsonders.com
www.hollgysonders.com
www.hollhsonders.com
www.hollyhsonders.com
www.hollhysonders.com
www.hollusonders.com
www.hollyusonders.com
www.holluysonders.com
www.hollyonders.com
www.hollywonders.com
www.hollyswonders.com
www.hollywsonders.com
www.hollyeonders.com
www.hollyseonders.com
www.hollyesonders.com
www.hollydonders.com
www.hollysdonders.com
www.hollydsonders.com
www.hollyzonders.com
www.hollyszonders.com
www.hollyzsonders.com
www.hollyxonders.com
www.hollysxonders.com
www.hollyxsonders.com
www.hollyaonders.com
www.hollysaonders.com
www.hollyasonders.com
www.hollysnders.com
www.hollysinders.com
www.hollysoinders.com
www.hollysionders.com
www.hollysknders.com
www.hollysoknders.com
www.hollyskonders.com
www.hollyslnders.com
www.hollysolnders.com
www.hollyslonders.com
www.hollyspnders.com
www.hollysopnders.com
www.hollysponders.com
www.hollysoders.com
www.hollysobders.com
www.hollysonbders.com
www.hollysobnders.com
www.hollysohders.com
www.hollysonhders.com
www.hollysohnders.com
www.hollysojders.com
www.hollysonjders.com
www.hollysojnders.com
www.hollysomders.com
www.hollysonmders.com
www.hollysomnders.com
www.hollysoners.com
www.hollysonxers.com
www.hollysondxers.com
www.hollysonxders.com
www.hollysonsers.com
www.hollysondsers.com
www.hollysonsders.com
www.hollysoneers.com
www.hollysondeers.com
www.hollysoneders.com
www.hollysonrers.com
www.hollysondrers.com
www.hollysonrders.com
www.hollysonfers.com
www.hollysondfers.com
www.hollysonfders.com
www.hollysoncers.com
www.hollysondcers.com
www.hollysoncders.com
www.hollysondrs.com
www.hollysondwrs.com
www.hollysondewrs.com
www.hollysondwers.com
www.hollysondsrs.com
www.hollysondesrs.com
www.hollysonddrs.com
www.hollysondedrs.com
www.hollysondders.com
www.hollysondrrs.com
www.hollysonderrs.com
www.hollysondes.com
www.hollysondees.com
www.hollysonderes.com
www.hollysondeds.com
www.hollysonderds.com
www.hollysondefs.com
www.hollysonderfs.com
www.hollysondefrs.com
www.hollysondets.com
www.hollysonderts.com
www.hollysondetrs.com
www.hollysonder.com
www.hollysonderw.com
www.hollysondersw.com
www.hollysonderws.com
www.hollysondere.com
www.hollysonderse.com
www.hollysonderd.com
www.hollysondersd.com
www.hollysonderz.com
www.hollysondersz.com
www.hollysonderzs.com
www.hollysonderx.com
www.hollysondersx.com
www.hollysonderxs.com
www.hollysondera.com
www.hollysondersa.com
www.hollysonderas.com
www.hollysonders.con
www.hollysonders.net
www.hollysonders.org
www.hollysonders.info
www.hollysonders.biz
www.hollysonders.us
www.hollysonders.mobi
www.ollysonders.com
www.hollysonders.com
www.bollysonders.com
www.hbollysonders.com
www.bhollysonders.com
www.gollysonders.com
www.hgollysonders.com
www.ghollysonders.com
www.yollysonders.com
www.hyollysonders.com
www.yhollysonders.com
www.uollysonders.com
www.huollysonders.com
www.uhollysonders.com
www.jollysonders.com
www.hjollysonders.com
www.jhollysonders.com
www.nollysonders.com
www.hnollysonders.com
www.nhollysonders.com
www.hllysonders.com
www.hillysonders.com
www.hoillysonders.com
www.hiollysonders.com
www.hkllysonders.com
www.hokllysonders.com
www.hkollysonders.com
www.hlllysonders.com
www.holllysonders.com
www.hlollysonders.com
www.hpllysonders.com
www.hopllysonders.com
www.hpollysonders.com
www.holysonders.com
www.hoplysonders.com
www.holplysonders.com
www.hoolysonders.com
www.hololysonders.com
www.hoollysonders.com
www.hoklysonders.com
www.holklysonders.com
www.holpysonders.com
www.hollpysonders.com
www.holoysonders.com
www.holloysonders.com
www.holkysonders.com
www.hollkysonders.com
www.hollsonders.com
www.holltsonders.com
www.hollytsonders.com
www.holltysonders.com
www.hollgsonders.com
www.hollygsonders.com
www.hollgysonders.com
www.hollhsonders.com
www.hollyhsonders.com
www.hollhysonders.com
www.hollusonders.com
www.hollyusonders.com
www.holluysonders.com
www.hollyonders.com
www.hollywonders.com
www.hollyswonders.com
www.hollywsonders.com
www.hollyeonders.com
www.hollyseonders.com
www.hollyesonders.com
www.hollydonders.com
www.hollysdonders.com
www.hollydsonders.com
www.hollyzonders.com
www.hollyszonders.com
www.hollyzsonders.com
www.hollyxonders.com
www.hollysxonders.com
www.hollyxsonders.com
www.hollyaonders.com
www.hollysaonders.com
www.hollyasonders.com
www.hollysnders.com
www.hollysinders.com
www.hollysoinders.com
www.hollysionders.com
www.hollysknders.com
www.hollysoknders.com
www.hollyskonders.com
www.hollyslnders.com
www.hollysolnders.com
www.hollyslonders.com
www.hollyspnders.com
www.hollysopnders.com
www.hollysponders.com
www.hollysoders.com
www.hollysobders.com
www.hollysonbders.com
www.hollysobnders.com
www.hollysohders.com
www.hollysonhders.com
www.hollysohnders.com
www.hollysojders.com
www.hollysonjders.com
www.hollysojnders.com
www.hollysomders.com
www.hollysonmders.com
www.hollysomnders.com
www.hollysoners.com
www.hollysonxers.com
www.hollysondxers.com
www.hollysonxders.com
www.hollysonsers.com
www.hollysondsers.com
www.hollysonsders.com
www.hollysoneers.com
www.hollysondeers.com
www.hollysoneders.com
www.hollysonrers.com
www.hollysondrers.com
www.hollysonrders.com
www.hollysonfers.com
www.hollysondfers.com
www.hollysonfders.com
www.hollysoncers.com
www.hollysondcers.com
www.hollysoncders.com
www.hollysondrs.com
www.hollysondwrs.com
www.hollysondewrs.com
www.hollysondwers.com
www.hollysondsrs.com
www.hollysondesrs.com
www.hollysonddrs.com
www.hollysondedrs.com
www.hollysondders.com
www.hollysondrrs.com
www.hollysonderrs.com
www.hollysondes.com
www.hollysondees.com
www.hollysonderes.com
www.hollysondeds.com
www.hollysonderds.com
www.hollysondefs.com
www.hollysonderfs.com
www.hollysondefrs.com
www.hollysondets.com
www.hollysonderts.com
www.hollysondetrs.com
www.hollysonder.com
www.hollysonderw.com
www.hollysondersw.com
www.hollysonderws.com
www.hollysondere.com
www.hollysonderse.com
www.hollysonderd.com
www.hollysondersd.com
www.hollysonderz.com
www.hollysondersz.com
www.hollysonderzs.com
www.hollysonderx.com
www.hollysondersx.com
www.hollysonderxs.com
www.hollysondera.com
www.hollysondersa.com
www.hollysonderas.com
www.hollysonders.con