Tools & Wizards About Us
gransier.nl screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

gransier.nl

Welkom bij Gransier BV

Page Load Speed

3.1 sec in total

First Response

367 ms

Resources Loaded

2.5 sec

Page Rendered

262 ms

gransier.nl screenshot

About Website

Welcome to gransier.nl homepage info - get ready to check Gransier best content for Netherlands right away, or after learning these important things about gransier.nl

Groothandel, import en export van fietsen, onderdelen en accessoires voor fiets, bromfiets en scooter.

Visit gransier.nl

Key Findings

We analyzed Gransier.nl page load time and found that the first response time was 367 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

gransier.nl performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value22.2 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value5,170 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.354

31/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

gransier.nl

367 ms

www.gransier.nl

763 ms

amshopby.css

96 ms

csvcart.css

184 ms

quickorder.css

184 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 89% of them (56 requests) were addressed to the original Gransier.nl, 6% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (856 ms) belongs to the original domain Gransier.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (66%)

Content Size

2.2 MB

After Optimization

758.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gransier.nl main page is 2.2 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. 55% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 44.1 kB

  • Original 53.4 kB
  • After minification 45.7 kB
  • After compression 9.2 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 7.7 kB, which is 14% 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 44.1 kB or 83% of the original size.

Image Optimization

-23%

Potential reduce by 133.1 kB

  • Original 583.3 kB
  • After minification 450.2 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, Gransier needs image optimization as it can save up to 133.1 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-78%

Potential reduce by 860.5 kB

  • Original 1.1 MB
  • After minification 827.1 kB
  • After compression 241.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 860.5 kB or 78% of the original size.

CSS Optimization

-88%

Potential reduce by 404.3 kB

  • Original 461.7 kB
  • After minification 391.4 kB
  • After compression 57.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. Gransier.nl needs all CSS files to be minified and compressed as it can save up to 404.3 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (63%)

Requests Now

56

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gransier.nl

gransier.nl

367 ms

www.gransier.nl

www.gransier.nl

763 ms

amshopby.css

amshopby.css

96 ms

csvcart.css

csvcart.css

184 ms

quickorder.css

quickorder.css

184 ms

glyphicons.css

glyphicons.css

192 ms

styles.css

styles.css

187 ms

mirasvit_banner.css

mirasvit_banner.css

184 ms

mirasvit_searchindex.css

mirasvit_searchindex.css

193 ms

style.css

style.css

455 ms

prototype.js

prototype.js

479 ms

ccard.js

ccard.js

278 ms

validation.js

validation.js

278 ms

builder.js

builder.js

278 ms

effects.js

effects.js

280 ms

dragdrop.js

dragdrop.js

370 ms

controls.js

controls.js

372 ms

slider.js

slider.js

372 ms

js.js

js.js

373 ms

form.js

form.js

476 ms

translate.js

translate.js

477 ms

cookies.js

cookies.js

477 ms

jquery.min.js

jquery.min.js

559 ms

underscore.js

underscore.js

543 ms

backbone.js

backbone.js

545 ms

jquery-ui.js

jquery-ui.js

825 ms

easing.js

easing.js

555 ms

tabbed.js

tabbed.js

557 ms

carousel.js

carousel.js

634 ms

side_carousel.js

side_carousel.js

635 ms

form.js

form.js

649 ms

autocomplete.js

autocomplete.js

649 ms

event.simulate.js

event.simulate.js

651 ms

csvcart.js

csvcart.js

725 ms

quickorder.js

quickorder.js

726 ms

script.js

script.js

856 ms

jquery.menu-aim.js

jquery.menu-aim.js

743 ms

css

css

24 ms

ga.js

ga.js

40 ms

logo.png

logo.png

188 ms

de.png

de.png

101 ms

dk.png

dk.png

105 ms

es.png

es.png

103 ms

fr.png

fr.png

104 ms

nl.png

nl.png

103 ms

uk.png

uk.png

184 ms

gransier-pand.png

gransier-pand.png

276 ms

Beta.jpg

Beta.jpg

371 ms

0cbe2b2915f209c2b6a2f1e8c9223fe9.jpg

0cbe2b2915f209c2b6a2f1e8c9223fe9.jpg

194 ms

d6fda4104320b77e36934916805450dd.jpg

d6fda4104320b77e36934916805450dd.jpg

196 ms

29b11584d91a3251daeedda97360b738.png

29b11584d91a3251daeedda97360b738.png

275 ms

11f095c7372cb6430617532ea2b5927e.jpg

11f095c7372cb6430617532ea2b5927e.jpg

279 ms

650302-1.jpg

650302-1.jpg

286 ms

309055.jpg

309055.jpg

290 ms

137911.jpg

137911.jpg

367 ms

81727000-5.jpg

81727000-5.jpg

369 ms

500394.jpg

500394.jpg

372 ms

K95WapF0Wa6u7CY0wsZbXqCWcynf_cDxXwCLxiixG1c.ttf

K95WapF0Wa6u7CY0wsZbXqCWcynf_cDxXwCLxiixG1c.ttf

71 ms

ngiFXK5ukde3w4E-Lmb_OnYhjbSpvc47ee6xR_80Hnw.ttf

ngiFXK5ukde3w4E-Lmb_OnYhjbSpvc47ee6xR_80Hnw.ttf

71 ms

hFqlepBer-IXtJK7U5poiXYhjbSpvc47ee6xR_80Hnw.ttf

hFqlepBer-IXtJK7U5poiXYhjbSpvc47ee6xR_80Hnw.ttf

75 ms

F-JaJbplW75-CW3MZ1qMbnYhjbSpvc47ee6xR_80Hnw.ttf

F-JaJbplW75-CW3MZ1qMbnYhjbSpvc47ee6xR_80Hnw.ttf

75 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

440 ms

__utm.gif

__utm.gif

36 ms

Accessibility Review

gransier.nl accessibility score

84

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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

<frame> or <iframe> elements do not have a title

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

gransier.nl best practices score

50

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

High

Serves images with low resolution

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

gransier.nl SEO score

85

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

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gransier.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch 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 Gransier.nl 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

gransier.nl

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