Tools & Wizards About Us
leefiori.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

leefiori.com

Everyday Jewelry, Rings, Necklaces, Bracelets, Earrings | Lee Fiori

Page Load Speed

634 ms in total

First Response

192 ms

Resources Loaded

442 ms

Page Rendered

0 ms

leefiori.com screenshot

About Website

Visit leefiori.com now to see the best up-to-date Lee Fiori content and also check out these interesting facts you probably never knew about leefiori.com

Everyday fine jewelry made just for you at below retail prices. Enjoy our curated looks or customize your own. Hand crafted in Toronto. Free Shipping and 99-Day Returns!

Visit leefiori.com

Key Findings

We analyzed Leefiori.com page load time and found that the first response time was 192 ms and then it took 442 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

leefiori.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value3,430 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

www.leefiori.com

192 ms

gtm.js

88 ms

search-aeb75d2d7fad098090f7.svg

71 ms

jewlr.gif

41 ms

logo-f0829a9c23106d818a8d.svg

83 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 9% of them (1 request) were addressed to the original Leefiori.com, 45% (5 requests) were made to Cdn.jewlr.com and 18% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (192 ms) belongs to the original domain Leefiori.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 69.6 kB (11%)

Content Size

607.3 kB

After Optimization

537.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Leefiori.com main page is 607.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 340.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 69.6 kB

  • Original 86.6 kB
  • After minification 86.5 kB
  • After compression 17.0 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 69.6 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 340.5 kB
  • After minification 340.5 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Lee Fiori images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 180.3 kB
  • After minification 180.3 kB
  • After compression 180.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 4 (40%)

Requests Now

10

After Optimization

6

  • Images
  • JavaScript

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lee Fiori. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.leefiori.com

www.leefiori.com

192 ms

gtm.js

gtm.js

88 ms

search-aeb75d2d7fad098090f7.svg

search-aeb75d2d7fad098090f7.svg

71 ms

jewlr.gif

jewlr.gif

41 ms

logo-f0829a9c23106d818a8d.svg

logo-f0829a9c23106d818a8d.svg

83 ms

desktop_2x_a9db44af73.jpg

desktop_2x_a9db44af73.jpg

137 ms

runtime-b2b596ab18c14f636ce5.js

runtime-b2b596ab18c14f636ce5.js

138 ms

7675-2df5ae8ef1f8dc3c76b5.js

7675-2df5ae8ef1f8dc3c76b5.js

109 ms

application-d3a8a9a38b9934d1646b.js

application-d3a8a9a38b9934d1646b.js

108 ms

desktop_3d5ac2c5cb.svg

desktop_3d5ac2c5cb.svg

177 ms

js

js

61 ms

Accessibility Review

leefiori.com accessibility score

83

Accessibility Issues

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.

Impact

Issue

High

[role]s are not contained by their required parent element

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

leefiori.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

leefiori.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leefiori.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Leefiori.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

leefiori.com

Open Graph description is not detected on the main page of Lee Fiori. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: