Lizzys.ca Site Title

Lizzy's by Cathy Allan | Dresses For Special Occasions

Lizzys.ca Meta Description

We make dress dreams come true. We've served Ontario & beyond special occasion ladies fashion for over 25 years. Welcome to Lizzy's.

Lizzys.ca Test Results

Lizzys.ca Mobile Performance: 72/100
Quick overview:
Forced reflow
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Document request latency
Est savings of 670 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Improve image delivery
Est savings of 372 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Network dependency tree
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.
Time to Interactive
9.4 s
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.
Use efficient cache lifetimes
Est savings of 97 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Legacy JavaScript
Est savings of 12 KiB
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
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce initial server response time
Root document took 610 ms
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.
Properly size images
Est savings of 291 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce unused CSS
Est savings of 27 KiB
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.
Largest Contentful Paint element
9,270 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Est savings of 135 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.
Avoid multiple page redirects
Est savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Avoid serving legacy JavaScript to modern browsers
Est savings of 12 KiB
Polyfills and transforms enable legacy 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 legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Avoid an excessive DOM size
2,099 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Serve static assets with an efficient cache policy
7 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Serve images in next-gen formats
Est savings of 24 KiB
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.
Does not use 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.
Avoid enormous network payloads
Total size was 2,738 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Lizzys.ca Mobile SEO: 100/100
Quick overview:

Lizzys.ca Mobile Best Practices: 79/100
Quick overview:
Trust and Safety
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 served over 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 about HTTPS.
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 about source maps.
User Experience
Serves images with low 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.
Lizzys.ca Mobile Accessibility: 87/100
Quick overview:
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.
Links do not 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 make links accessible.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is 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.
Touch targets do not have sufficient size or 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.
Similar sites
Similar tests
www.lizzys.com
www.lizzys.net
www.lizzys.org
www.lizzys.info
www.lizzys.biz
www.lizzys.us
www.lizzys.mobi
www.izzys.ca
www.lizzys.ca
www.pizzys.ca
www.lpizzys.ca
www.plizzys.ca
www.oizzys.ca
www.loizzys.ca
www.olizzys.ca
www.kizzys.ca
www.lkizzys.ca
www.klizzys.ca
www.lzzys.ca
www.luzzys.ca
www.liuzzys.ca
www.luizzys.ca
www.ljzzys.ca
www.lijzzys.ca
www.ljizzys.ca
www.lkzzys.ca
www.likzzys.ca
www.lozzys.ca
www.liozzys.ca
www.lizys.ca
www.lixzys.ca
www.lizxzys.ca
www.lixzzys.ca
www.liszys.ca
www.lizszys.ca
www.liszzys.ca
www.liazys.ca
www.lizazys.ca
www.liazzys.ca
www.lizxys.ca
www.lizzxys.ca
www.lizsys.ca
www.lizzsys.ca
www.lizays.ca
www.lizzays.ca
www.lizzs.ca
www.lizzts.ca
www.lizzyts.ca
www.lizztys.ca
www.lizzgs.ca
www.lizzygs.ca
www.lizzgys.ca
www.lizzhs.ca
www.lizzyhs.ca
www.lizzhys.ca
www.lizzus.ca
www.lizzyus.ca
www.lizzuys.ca
www.lizzy.ca
www.lizzyw.ca
www.lizzysw.ca
www.lizzyws.ca
www.lizzye.ca
www.lizzyse.ca
www.lizzyes.ca
www.lizzyd.ca
www.lizzysd.ca
www.lizzyds.ca
www.lizzyz.ca
www.lizzysz.ca
www.lizzyzs.ca
www.lizzyx.ca
www.lizzysx.ca
www.lizzyxs.ca
www.lizzya.ca
www.lizzysa.ca
www.lizzyas.ca
Last Tested: