Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

stonescanner.com

Bstone Scanner-scan stone & ceramic tile in high definition

Page Load Speed

1 sec in total

First Response

26 ms

Resources Loaded

750 ms

Page Rendered

232 ms

About Website

Click here to check amazing Stone Scanner content. Otherwise, check out these important facts you probably never knew about stonescanner.com

Adopted the most advanced image CIS and precise infrared filter technology, Bstone Scanner can scan stone images in high definition without any color concerns anywhere and anytime. It can replace ston...

Visit stonescanner.com

Key Findings

We analyzed Stonescanner.com page load time and found that the first response time was 26 ms and then it took 982 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

stonescanner.com performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

stonescanner.com

26 ms

stonescanner.com

196 ms

hdpicture.css

84 ms

magnific-popup.css

99 ms

jquery.min.js

113 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that all of those requests were addressed to Stonescanner.com and no external sources were called. The less responsive or slowest element that took the longest time to load (325 ms) belongs to the original domain Stonescanner.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 271.3 kB (10%)

Content Size

2.8 MB

After Optimization

2.5 MB

In fact, the total size of Stonescanner.com main page is 2.8 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. 65% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 27.5 kB

  • Original 32.5 kB
  • After minification 21.4 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 11.1 kB, which is 34% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 27.5 kB or 85% of the original size.

Image Optimization

-8%

Potential reduce by 215.2 kB

  • Original 2.7 MB
  • After minification 2.5 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. Stone Scanner images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 21.0 kB

  • Original 70.2 kB
  • After minification 70.2 kB
  • After compression 49.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 21.0 kB or 30% of the original size.

CSS Optimization

-47%

Potential reduce by 7.6 kB

  • Original 16.2 kB
  • After minification 16.2 kB
  • After compression 8.6 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. Stonescanner.com needs all CSS files to be minified and compressed as it can save up to 7.6 kB or 47% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (33%)

Requests Now

24

After Optimization

16

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

Accessibility Review

stonescanner.com accessibility score

57

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

stonescanner.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

stonescanner.com SEO score

58

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stonescanner.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Stonescanner.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 description is not detected on the main page of Stone Scanner. 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: