Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ijskar.nl

Roberto Gelato - Ice cream freaks in Utrecht

Page Load Speed

4.7 sec in total

First Response

346 ms

Resources Loaded

3.4 sec

Page Rendered

1 sec

ijskar.nl screenshot

About Website

Visit ijskar.nl now to see the best up-to-date Ijskar content and also check out these interesting facts you probably never knew about ijskar.nl

Roberto maakt van maart tot oktober, iedere dag heerlijk ijs met de lekkerste ingrediënten voor de ijssalon. Puur, vers, liefst lokaal, altijd ambachtelijk

Visit ijskar.nl

Key Findings

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

Performance Metrics

ijskar.nl performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

ijskar.nl

346 ms

www.lekkerijs.nl

1324 ms

style.css

180 ms

css

24 ms

css

35 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ijskar.nl, 50% (56 requests) were made to Lekkerijs.nl and 21% (24 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Lekkerijs.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 844.4 kB (12%)

Content Size

6.9 MB

After Optimization

6.0 MB

In fact, the total size of Ijskar.nl main page is 6.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 156.5 kB

  • Original 190.6 kB
  • After minification 174.8 kB
  • After compression 34.1 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 156.5 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 45.0 kB

  • Original 5.7 MB
  • After minification 5.6 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. Ijskar images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 602.0 kB

  • Original 971.2 kB
  • After minification 949.3 kB
  • After compression 369.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 602.0 kB or 62% of the original size.

CSS Optimization

-85%

Potential reduce by 41.0 kB

  • Original 48.0 kB
  • After minification 33.8 kB
  • After compression 7.0 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. Ijskar.nl needs all CSS files to be minified and compressed as it can save up to 41.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (43%)

Requests Now

103

After Optimization

59

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

Accessibility Review

ijskar.nl accessibility score

76

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.

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

ijskar.nl 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ijskar.nl SEO score

83

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ijskar.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Ijskar.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

Open Graph data is detected on the main page of Ijskar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: