8.7 sec in total
269 ms
7.8 sec
594 ms
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.comWe analyzed Faystone.com page load time and found that the first response time was 269 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
faystone.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value11.6 s
0/100
25%
Value12.8 s
2/100
10%
Value4,520 ms
0/100
30%
Value0.128
82/100
15%
Value11.7 s
18/100
10%
269 ms
2346 ms
31 ms
570 ms
353 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 84% of them (51 requests) were addressed to the original Faystone.com, 8% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Faystone.com.
Page size can be reduced by 482.5 kB (5%)
9.5 MB
9.0 MB
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. 70% of websites need less resources to load. Images take 9.1 MB which makes up the majority of the site volume.
Potential reduce by 54.7 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 54.7 kB or 82% of the original size.
Potential reduce by 377.8 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. FAYSTONE images are well optimized though.
Potential reduce by 41.6 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 41.6 kB or 29% of the original size.
Potential reduce by 8.4 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.
Number of requests can be reduced by 33 (63%)
52
19
The browser has sent 52 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 20 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
faystone.com
269 ms
faystone.com
2346 ms
wp-emoji-release.min.js
31 ms
style.min.css
570 ms
wc-blocks-vendors-style.css
353 ms
wc-blocks-style.css
651 ms
css
54 ms
wishlist_style.css
379 ms
woocommerce-layout.css
491 ms
woocommerce.css
543 ms
style.dev.css
1281 ms
style.css
807 ms
css
65 ms
shortcodes_responsive.css
801 ms
magnific_popup.css
855 ms
dashicons.min.css
1067 ms
jquery.min.js
669 ms
jquery-migrate.min.js
972 ms
sharethis.js
1130 ms
et-divi-customizer-global-166359287927.min.css
1125 ms
email-decode.min.js
857 ms
frontend-builder-global-functions.js
867 ms
wishlist_js.js
878 ms
jquery.blockUI.min.js
890 ms
add-to-cart.min.js
1210 ms
js.cookie.min.js
1705 ms
woocommerce.min.js
1707 ms
cart-fragments.min.js
1708 ms
jquery.mobile.custom.min.js
1709 ms
custom.js
2059 ms
smoothscroll.js
2057 ms
jquery.fitvids.js
1704 ms
waypoints.min.js
1704 ms
jquery.magnific-popup.js
2058 ms
frontend-builder-scripts.js
2221 ms
common.js
1707 ms
faystone-logo-1c-1.png
630 ms
cards.png
561 ms
espa-banner-scaled.jpg
592 ms
analytics.js
423 ms
S6uyw4BMUTPHjx4wWA.woff
147 ms
S6u9w4BMUTPHh7USSwiPHw.woff
311 ms
S6u8w4BMUTPHh30AXC-s.woff
774 ms
S6u9w4BMUTPHh6UVSwiPHw.woff
804 ms
S6u9w4BMUTPHh50XSwiPHw.woff
805 ms
modules.ttf
807 ms
collect
708 ms
Banner-Andromeda-for-WEB.jpg
858 ms
Banner-Elegance-for-WEB.jpg
871 ms
Banner-Chair-for-Web.jpg
906 ms
neckleses.jpg
903 ms
Banner-Mirror-WEB.jpg
867 ms
BANNER-PENDANT-for-WEB.jpg
869 ms
Banner-White-for-web.jpg
1612 ms
neckleses-final-16-9.jpg
1805 ms
PENDANTS_JEWELLERY.jpg
1624 ms
Faystone_Jewels_Rings.jpg
1850 ms
bracelets-web.jpg
1775 ms
collect
559 ms
faystone.com
1822 ms
woocommerce-smallscreen.css
311 ms
faystone.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
faystone.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
faystone.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
EN
EN
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.
faystone.com
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: