Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

stonestones.rocks

Studio Mineralia connects Minerals, Crystals & Art.

Page Load Speed

1.9 sec in total

First Response

90 ms

Resources Loaded

1.7 sec

Page Rendered

56 ms

stonestones.rocks screenshot

About Website

Welcome to stonestones.rocks homepage info - get ready to check Stonestones best content right away, or after learning these important things about stonestones.rocks

Studio Mineralia Connects Minerals, Crystals & Art, Using Geology As Our Guiding Aesthetic Principle.

Visit stonestones.rocks

Key Findings

We analyzed Stonestones.rocks page load time and found that the first response time was 90 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

stonestones.rocks performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

www.studiomineralia.com

90 ms

minified.js

29 ms

focus-within-polyfill.js

29 ms

polyfill.min.js

844 ms

thunderbolt-commons.7700cd07.bundle.min.js

57 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Stonestones.rocks, 29% (12 requests) were made to Sentry-next.wixpress.com and 7% (3 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (844 ms) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 886.9 kB (47%)

Content Size

1.9 MB

After Optimization

996.9 kB

In fact, the total size of Stonestones.rocks main page is 1.9 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. 30% of websites need less resources to load. Images take 821.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 602.9 kB

  • Original 758.3 kB
  • After minification 756.5 kB
  • After compression 155.4 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 602.9 kB or 80% of the original size.

Image Optimization

-29%

Potential reduce by 235.6 kB

  • Original 821.3 kB
  • After minification 585.7 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. Obviously, Stonestones needs image optimization as it can save up to 235.6 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 48.3 kB

  • Original 304.2 kB
  • After minification 304.2 kB
  • After compression 255.8 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 48.3 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (60%)

Requests Now

20

After Optimization

8

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

Accessibility Review

stonestones.rocks accessibility score

100

Accessibility Issues

Best Practices

stonestones.rocks 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

High

Page has valid source maps

SEO Factors

stonestones.rocks SEO score

88

Search Engine Optimization Advices

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Stonestones.rocks 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 Stonestones.rocks 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 Stonestones. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: