Tools & Wizards About Us
slim.nl screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

slim.nl

Slim

Page Load Speed

4.1 sec in total

First Response

200 ms

Resources Loaded

3.5 sec

Page Rendered

349 ms

slim.nl screenshot

About Website

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

Slim.nl is dé webwinkel voor het middelbaar (beroeps)onderwijs, met hoge korting op al je software en hardware zoals Microsoft Office. Jouw school werkt samen met Slim.nl; profiteer hiervan! Voor doce...

Visit slim.nl

Key Findings

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

Performance Metrics

slim.nl performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value16.8 s

0/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.542

13/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

slim.nl

200 ms

default.aspx

1888 ms

module.css

176 ms

default.css

389 ms

skin.css

565 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 641.2 kB (56%)

Content Size

1.2 MB

After Optimization

512.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Slim.nl main page is 1.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. 35% of websites need less resources to load. Javascripts take 589.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 75.4 kB

  • Original 95.5 kB
  • After minification 88.5 kB
  • After compression 20.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 75.4 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 15.1 kB

  • Original 323.7 kB
  • After minification 308.6 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. Slim images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 429.4 kB

  • Original 589.4 kB
  • After minification 552.1 kB
  • After compression 160.1 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 429.4 kB or 73% of the original size.

CSS Optimization

-84%

Potential reduce by 121.4 kB

  • Original 144.9 kB
  • After minification 113.7 kB
  • After compression 23.5 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. Slim.nl needs all CSS files to be minified and compressed as it can save up to 121.4 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

57

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

slim.nl

slim.nl

200 ms

default.aspx

default.aspx

1888 ms

module.css

module.css

176 ms

default.css

default.css

389 ms

skin.css

skin.css

565 ms

container.css

container.css

315 ms

portal.css

portal.css

318 ms

jquery.min.js

jquery.min.js

690 ms

ComboBox.Default.css

ComboBox.Default.css

903 ms

jquery-ui.min.js

jquery-ui.min.js

657 ms

WebResource.axd

WebResource.axd

218 ms

dnncore.js

dnncore.js

294 ms

dnn.modalpopup.js

dnn.modalpopup.js

297 ms

SlimControls.js

SlimControls.js

382 ms

gtm-ee.min.js

gtm-ee.min.js

377 ms

jquery.hoverIntent.min.js

jquery.hoverIntent.min.js

457 ms

dnn.jquery.js

dnn.jquery.js

470 ms

ScriptResource.axd

ScriptResource.axd

477 ms

ScriptResource.axd

ScriptResource.axd

615 ms

ScriptResource.axd

ScriptResource.axd

557 ms

LoginAndBasket.js

LoginAndBasket.js

571 ms

jquery.watermarkinput.js

jquery.watermarkinput.js

593 ms

jquery.cycle.min.js

jquery.cycle.min.js

553 ms

initWidgets.js

initWidgets.js

547 ms

logo.png

logo.png

189 ms

hp-pavilion-x360-13-S105nd-klein.png

hp-pavilion-x360-13-S105nd-klein.png

97 ms

arrow_blue.png

arrow_blue.png

83 ms

magix%20web-designer-11.png

magix%20web-designer-11.png

174 ms

white_arrow.png

white_arrow.png

89 ms

Microsoft%20Office%20Professional%20Plus%202016%20placeholder.png

Microsoft%20Office%20Professional%20Plus%202016%20placeholder.png

82 ms

norton-security-premium-2016.png

norton-security-premium-2016.png

163 ms

iphone-5-180x180.png

iphone-5-180x180.png

158 ms

xoopar-powerbank-squid-zilver-2.png

xoopar-powerbank-squid-zilver-2.png

176 ms

microsoft-windows-10-education.png

microsoft-windows-10-education.png

185 ms

corel-winzip-20.png

corel-winzip-20.png

234 ms

microsoft-office-for-mac-2016-placeholder.png

microsoft-office-for-mac-2016-placeholder.png

237 ms

kaspersky-internet-security-multi-device-2016.png

kaspersky-internet-security-multi-device-2016.png

256 ms

adobe-creative-cloud-nieuw.png

adobe-creative-cloud-nieuw.png

260 ms

beats-by-dr-dre-solo-hd-red-klein.png

beats-by-dr-dre-solo-hd-red-klein.png

368 ms

ozobot-2.0-klein.png

ozobot-2.0-klein.png

276 ms

apple_logo.png

apple_logo.png

310 ms

twitter_icon.png

twitter_icon.png

316 ms

facebook_icon.png

facebook_icon.png

339 ms

slbdiensten_logo.png

slbdiensten_logo.png

345 ms

shopping_cart.png

shopping_cart.png

317 ms

nettoot-bold-webfont.woff

nettoot-bold-webfont.woff

337 ms

search_icon.png

search_icon.png

344 ms

worksmart-header.png

worksmart-header.png

731 ms

blue_no_shadow_l.png

blue_no_shadow_l.png

372 ms

blue_no_shadow_r.png

blue_no_shadow_r.png

379 ms

white_arrow.png

white_arrow.png

406 ms

nettoot-light-webfont.woff

nettoot-light-webfont.woff

400 ms

nettoot-webfont.woff

nettoot-webfont.woff

415 ms

prodcut_price_bg.png

prodcut_price_bg.png

415 ms

more_info_arrow.png

more_info_arrow.png

449 ms

panel_nav_arrow.png

panel_nav_arrow.png

448 ms

register_blue_right_btn.png

register_blue_right_btn.png

472 ms

green_twiter.png

green_twiter.png

476 ms

green_facebook.png

green_facebook.png

467 ms

list_arrow.png

list_arrow.png

464 ms

DotNetNukeAjaxShared.js

DotNetNukeAjaxShared.js

510 ms

widgets.js

widgets.js

102 ms

Accessibility Review

slim.nl accessibility score

73

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

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

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

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

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

slim.nl SEO score

92

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

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

    NL

  • Encoding

    UTF-8

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

slim.nl

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