Tools & Wizards About Us
oozo.nl screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

oozo.nl

Laatste regionale nieuws en 112 berichten Nederland - Oozo.nl

Page Load Speed

6.5 sec in total

First Response

196 ms

Resources Loaded

5.5 sec

Page Rendered

783 ms

oozo.nl screenshot

About Website

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

Van het laatste regionale nieuws en P2000 meldingen van politie, brandweer en ambulance tot nieuw opgerichte bedrijven en afgegeven vergunningen in Nederland.

Visit oozo.nl

Key Findings

We analyzed Oozo.nl page load time and found that the first response time was 196 ms and then it took 6.3 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

oozo.nl performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value2,900 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.076

95/100

15%

TTI (Time to Interactive)

Value26.8 s

0/100

10%

Network Requests Diagram

oozo.nl

196 ms

www.oozo.nl

1472 ms

yit.js

429 ms

sharethis.js

26 ms

varify.js

100 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 40% of them (32 requests) were addressed to the original Oozo.nl, 32% (26 requests) were made to Cdn.binqmedia.nl and 5% (4 requests) were made to Dvhn.nl. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Cdn.binqmedia.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 371.4 kB (10%)

Content Size

3.6 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oozo.nl main page is 3.6 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. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 62.9 kB

  • Original 76.0 kB
  • After minification 65.6 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 10.3 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 62.9 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 266.9 kB

  • Original 3.3 MB
  • After minification 3.0 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. Oozo images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 38.5 kB

  • Original 205.0 kB
  • After minification 205.0 kB
  • After compression 166.5 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 38.5 kB or 19% of the original size.

CSS Optimization

-8%

Potential reduce by 3.1 kB

  • Original 37.5 kB
  • After minification 37.5 kB
  • After compression 34.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. Oozo.nl has all CSS files already compressed.

Requests Breakdown

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

Requests Now

70

After Optimization

37

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oozo.nl

oozo.nl

196 ms

www.oozo.nl

www.oozo.nl

1472 ms

yit.js

yit.js

429 ms

sharethis.js

sharethis.js

26 ms

varify.js

varify.js

100 ms

js

js

55 ms

jquery-ui.min.css

jquery-ui.min.css

97 ms

bootstrap.min.css

bootstrap.min.css

194 ms

Site.css

Site.css

331 ms

font-awesome.min.css

font-awesome.min.css

390 ms

MicrosoftAjax.js

MicrosoftAjax.js

584 ms

modernizr-2.6.2.js

modernizr-2.6.2.js

490 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

677 ms

jquery-ui.min.js

jquery-ui.min.js

696 ms

jquery.maxlength.min.js

jquery.maxlength.min.js

426 ms

bootstrap.min.js

bootstrap.min.js

483 ms

toolbox.js

toolbox.js

521 ms

ac.js

ac.js

578 ms

lozad.min.js

lozad.min.js

675 ms

ambulance_1-24.jpg

ambulance_1-24.jpg

715 ms

20f54e84-67f3-11ec-b2a6-0255c322e81b.jpg

20f54e84-67f3-11ec-b2a6-0255c322e81b.jpg

164 ms

z4kx338awvfm_wd1280.jpg

z4kx338awvfm_wd1280.jpg

778 ms

logo2.png

logo2.png

286 ms

mnuicnhome.png

mnuicnhome.png

286 ms

mnuicnoverzicht.png

mnuicnoverzicht.png

303 ms

mnuicncijfers.png

mnuicncijfers.png

303 ms

mnuicnhulpdiensten.png

mnuicnhulpdiensten.png

304 ms

mnuicnnieuws.png

mnuicnnieuws.png

355 ms

mnuicnbedrijven.png

mnuicnbedrijven.png

396 ms

mnuicnvideo.png

mnuicnvideo.png

396 ms

mnuicnwonen.png

mnuicnwonen.png

397 ms

mnuicngezondheid.png

mnuicngezondheid.png

397 ms

mnuicnevenement.png

mnuicnevenement.png

401 ms

mnuicnvergunningen.png

mnuicnvergunningen.png

435 ms

noimagewhite.png

noimagewhite.png

471 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

384 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

194 ms

12399229.jpg

12399229.jpg

527 ms

verhuiskaart-met-plaatsnaambord.jpg

verhuiskaart-met-plaatsnaambord.jpg

927 ms

stethoscope-840125_960_720.jpg

stethoscope-840125_960_720.jpg

90 ms

324 ms

Eelde%20Schiphol%20en%20Jonas.JPG

Eelde%20Schiphol%20en%20Jonas.JPG

76 ms

Buurtpreventie.jpg

Buurtpreventie.jpg

568 ms

hq720.jpg

hq720.jpg

401 ms

sdk.js

sdk.js

40 ms

12399228.jpg

12399228.jpg

1035 ms

12399230.jpg

12399230.jpg

1151 ms

12399224.jpg

12399224.jpg

1104 ms

12399225.jpg

12399225.jpg

937 ms

12399227.jpg

12399227.jpg

1027 ms

12399226.jpg

12399226.jpg

938 ms

12399221.jpg

12399221.jpg

1439 ms

12399223.jpg

12399223.jpg

1390 ms

12399219.jpg

12399219.jpg

1521 ms

12399220.jpg

12399220.jpg

1442 ms

12399212.jpg

12399212.jpg

1500 ms

12399216.jpg

12399216.jpg

1256 ms

1043521990.jpg

1043521990.jpg

1268 ms

1043521028.jpg

1043521028.jpg

1811 ms

1043522937.jpg

1043522937.jpg

1904 ms

7630_steekincident-zandvoort-lorentzstraat.png

7630_steekincident-zandvoort-lorentzstraat.png

2458 ms

7631_steekincident-nieuw-vennep-venneperweg.png

7631_steekincident-nieuw-vennep-venneperweg.png

1457 ms

7632_overval-supermarkt-amsterdamsestraatweg-utrecht.png

7632_overval-supermarkt-amsterdamsestraatweg-utrecht.png

2349 ms

4846650.jpg

4846650.jpg

1508 ms

4846655.jpg

4846655.jpg

2111 ms

4846653.jpg

4846653.jpg

2039 ms

2571561.jpg

2571561.jpg

2308 ms

574853.jpg

574853.jpg

2527 ms

2980413.jpg

2980413.jpg

2636 ms

3259314.jpg

3259314.jpg

2711 ms

noimage.png

noimage.png

154 ms

454 ms

335 ms

290c5da_w1272_tt46busassen%20%281%29.jpg

290c5da_w1272_tt46busassen%20%281%29.jpg

68 ms

hq720.jpg

hq720.jpg

377 ms

hq720.jpg

hq720.jpg

326 ms

flowers-276014_960_720.jpg

flowers-276014_960_720.jpg

133 ms

ui-bg_highlight-soft_100_eeeeee_1x100.png

ui-bg_highlight-soft_100_eeeeee_1x100.png

145 ms

sdk.js

sdk.js

11 ms

Eelde%20Schiphol%20en%20Jonas.JPG

Eelde%20Schiphol%20en%20Jonas.JPG

37 ms

290c5da_w1272_tt46busassen%20%281%29.jpg

290c5da_w1272_tt46busassen%20%281%29.jpg

69 ms

Accessibility Review

oozo.nl accessibility score

91

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

Image elements do not have [alt] attributes

Best Practices

oozo.nl best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Missing source maps for large first-party JavaScript

SEO Factors

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

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oozo.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 Oozo.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

oozo.nl

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