Tools & Wizards About Us
dunk.nl screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

dunk.nl

Home - Basketball.nl

Page Load Speed

4.1 sec in total

First Response

1.2 sec

Resources Loaded

2.6 sec

Page Rendered

343 ms

dunk.nl screenshot

About Website

Click here to check amazing Dunk content. Otherwise, check out these important facts you probably never knew about dunk.nl

Visit dunk.nl

Key Findings

We analyzed Dunk.nl page load time and found that the first response time was 1.2 sec and then it took 2.9 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

dunk.nl performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.1 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.6 s

1/100

10%

Network Requests Diagram

noord-holland

1172 ms

layout.css

501 ms

css

26 ms

jquery.fancybox-1.3.4.css

498 ms

nieuws.css

504 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Dunk.nl, 26% (9 requests) were made to Basketball.nl and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Basketball.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 214.1 kB (58%)

Content Size

368.6 kB

After Optimization

154.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dunk.nl main page is 368.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 172.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 28.8 kB

  • Original 36.2 kB
  • After minification 34.2 kB
  • After compression 7.4 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 28.8 kB or 80% of the original size.

Image Optimization

-30%

Potential reduce by 33.4 kB

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

JavaScript Optimization

-64%

Potential reduce by 110.2 kB

  • Original 172.2 kB
  • After minification 168.1 kB
  • After compression 62.0 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 110.2 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 41.7 kB

  • Original 48.4 kB
  • After minification 37.3 kB
  • After compression 6.8 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. Dunk.nl needs all CSS files to be minified and compressed as it can save up to 41.7 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

31

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

noord-holland

noord-holland

1172 ms

layout.css

layout.css

501 ms

css

css

26 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

498 ms

nieuws.css

nieuws.css

504 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

601 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

506 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

507 ms

jquery.mousewheel-3.0.4.pack.js

jquery.mousewheel-3.0.4.pack.js

593 ms

jquery.easing-1.3.pack.js

jquery.easing-1.3.pack.js

595 ms

logonbb.png

logonbb.png

107 ms

bg.jpg

bg.jpg

293 ms

inputtextbg.png

inputtextbg.png

108 ms

btnsearch.png

btnsearch.png

111 ms

tab1.png

tab1.png

110 ms

tab2.png

tab2.png

104 ms

tab3.png

tab3.png

108 ms

tab4.png

tab4.png

221 ms

tab5.png

tab5.png

233 ms

tab6.png

tab6.png

223 ms

menulogo_nbb.png

menulogo_nbb.png

233 ms

arrow_right.png

arrow_right.png

234 ms

listitem.png

listitem.png

317 ms

rss2.png

rss2.png

218 ms

masterz.jpg

masterz.jpg

423 ms

Header.jpg

Header.jpg

485 ms

LaatJeSportClubNietInZijnHemdStaan.jpg

LaatJeSportClubNietInZijnHemdStaan.jpg

402 ms

logo_fiba.png

logo_fiba.png

207 ms

logo_iwbf.png

logo_iwbf.png

208 ms

logo_nocnsf.png

logo_nocnsf.png

305 ms

analytics.js

analytics.js

12 ms

Y_TKV6o8WovbUd3m_X9aAA.ttf

Y_TKV6o8WovbUd3m_X9aAA.ttf

17 ms

bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf

bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf

16 ms

collect

collect

14 ms

collect

collect

54 ms

Accessibility Review

dunk.nl accessibility score

74

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dunk.nl SEO score

92

Search Engine Optimization Advices

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

dunk.nl

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