Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

granit.com

Granit - Inredning, förvaring och hemtextil i naturliga färger och hållbara material.

Page Load Speed

8 sec in total

First Response

1.2 sec

Resources Loaded

6.2 sec

Page Rendered

561 ms

granit.com screenshot

About Website

Click here to check amazing Granit content for Sweden. Otherwise, check out these important facts you probably never knew about granit.com

Granit - Skandinavisk inredning för hela hemmet i naturliga färger och material med inspiration från naturen. Bli medlem - Få 15% rabatt på första köpet!

Visit granit.com

Key Findings

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

Performance Metrics

granit.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value16.9 s

0/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value1,870 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value31.9 s

0/100

10%

Network Requests Diagram

www.granit.com

1216 ms

SE-util.js

124 ms

latest.pack.js

367 ms

form.js

381 ms

json.js

382 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 46% of them (56 requests) were addressed to the original Granit.com, 17% (21 requests) were made to Static.xx.fbcdn.net and 12% (15 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Granit.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 701.1 kB (38%)

Content Size

1.9 MB

After Optimization

1.2 MB

In fact, the total size of Granit.com 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. 60% of websites need less resources to load. Images take 964.7 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 143.2 kB

  • Original 159.0 kB
  • After minification 94.8 kB
  • After compression 15.8 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 64.3 kB, which is 40% 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 143.2 kB or 90% of the original size.

Image Optimization

-1%

Potential reduce by 4.8 kB

  • Original 964.7 kB
  • After minification 959.9 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. Granit images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 348.2 kB

  • Original 495.6 kB
  • After minification 438.6 kB
  • After compression 147.4 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 348.2 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 204.8 kB

  • Original 246.1 kB
  • After minification 196.7 kB
  • After compression 41.2 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. Granit.com needs all CSS files to be minified and compressed as it can save up to 204.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (47%)

Requests Now

120

After Optimization

64

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

Accessibility Review

granit.com accessibility score

82

Accessibility Issues

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

granit.com best practices score

58

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

granit.com SEO score

73

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    SV

  • Language Claimed

    SV

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Granit.com can be misinterpreted by Google and other search engines. Our service has detected that Swedish is used on the page, and it matches the claimed language. Our system also found out that Granit.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Granit. 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: