Tools & Wizards About Us

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

faystone.com

FAYSTONE Jewellery | Eclectic Handcrafted Jewellery

Page Load Speed

4.3 sec in total

First Response

251 ms

Resources Loaded

3.5 sec

Page Rendered

498 ms

About Website

Welcome to faystone.com homepage info - get ready to check FAYSTONE best content right away, or after learning these important things about faystone.com

Faystone Jewellery | Eclectic Handcrafted Jewellery with natural gemstones | Explore jewellery in a new, genuine, and unique way.

Visit faystone.com

Key Findings

We analyzed Faystone.com page load time and found that the first response time was 251 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

faystone.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.128

82/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

faystone.com

251 ms

faystone.com

1588 ms

wc-blocks-vendors-style.css

30 ms

wc-blocks-style.css

22 ms

css

30 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 85% of them (47 requests) were addressed to the original Faystone.com, 9% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Faystone.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 575.8 kB (6%)

Content Size

9.5 MB

After Optimization

8.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Faystone.com main page is 9.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 9.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 194.1 kB

  • Original 228.6 kB
  • After minification 225.3 kB
  • After compression 34.5 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 194.1 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 377.8 kB

  • Original 9.1 MB
  • After minification 8.7 MB

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. FAYSTONE images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.8 kB

  • Original 145.5 kB
  • After minification 145.5 kB
  • After compression 142.7 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.

CSS Optimization

-2%

Potential reduce by 1.1 kB

  • Original 57.0 kB
  • After minification 57.0 kB
  • After compression 55.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Faystone.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (64%)

Requests Now

47

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

faystone.com accessibility score

70

Accessibility Issues

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.

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.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

faystone.com best practices score

83

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

Browser errors were logged to the console

SEO Factors

faystone.com SEO score

69

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Faystone.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 Faystone.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

Open Graph data is detected on the main page of FAYSTONE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: