Tools & Wizards About Us
onna-onna.nl screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

onna-onna.nl

Alle informatie op een rij over de onna-onna verzekering

Page Load Speed

4.3 sec in total

First Response

380 ms

Resources Loaded

3.6 sec

Page Rendered

298 ms

onna-onna.nl screenshot

About Website

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

Onna-onna maakt onderdeel uit van Aegon. Heb jij als klant van onna-onna een schade? Of wil je jouw verzekering aanpassen?

Visit onna-onna.nl

Key Findings

We analyzed Onna-onna.nl page load time and found that the first response time was 380 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

onna-onna.nl performance score

0

Network Requests Diagram

onna-onna.nl

380 ms

www.onna-onna.nl

1077 ms

style.css

84 ms

app.css

263 ms

fonts.css

253 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 53% of them (39 requests) were addressed to the original Onna-onna.nl, 11% (8 requests) were made to Google.com and 10% (7 requests) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Onna-onna.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 479.7 kB (68%)

Content Size

707.3 kB

After Optimization

227.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onna-onna.nl main page is 707.3 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. 45% of websites need less resources to load. CSS take 323.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 47.5 kB

  • Original 59.4 kB
  • After minification 58.0 kB
  • After compression 11.9 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 47.5 kB or 80% of the original size.

Image Optimization

-14%

Potential reduce by 8.5 kB

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

JavaScript Optimization

-59%

Potential reduce by 154.9 kB

  • Original 263.8 kB
  • After minification 247.7 kB
  • After compression 109.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 154.9 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 268.8 kB

  • Original 323.3 kB
  • After minification 317.8 kB
  • After compression 54.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. Onna-onna.nl needs all CSS files to be minified and compressed as it can save up to 268.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (65%)

Requests Now

63

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onna-onna.nl

onna-onna.nl

380 ms

www.onna-onna.nl

www.onna-onna.nl

1077 ms

style.css

style.css

84 ms

app.css

app.css

263 ms

fonts.css

fonts.css

253 ms

cje7ozz.js

cje7ozz.js

258 ms

widget.css

widget.css

254 ms

font-awesome.min.css

font-awesome.min.css

260 ms

advanced-responsive-video-embedder-public.css

advanced-responsive-video-embedder-public.css

260 ms

jetpack.css

jetpack.css

340 ms

social-widget.css

social-widget.css

341 ms

jquery.min.js

jquery.min.js

89 ms

devicepx-jetpack.js

devicepx-jetpack.js

84 ms

gf.placeholders.js

gf.placeholders.js

352 ms

wp-embed.min.js

wp-embed.min.js

357 ms

jquery.json.js

jquery.json.js

352 ms

gravityforms.min.js

gravityforms.min.js

352 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

431 ms

home-service.js

home-service.js

431 ms

googlesitesearch.js

googlesitesearch.js

481 ms

jquery.colorbox.js

jquery.colorbox.js

487 ms

jquery.form.min.js

jquery.form.min.js

481 ms

jquery.validate.min.js

jquery.validate.min.js

505 ms

bootstrap.min.js

bootstrap.min.js

575 ms

bootstrap-hover-dropdown.min.js

bootstrap-hover-dropdown.min.js

573 ms

main.js

main.js

608 ms

2dab8e

2dab8e

114 ms

www.onna-onna.nl

www.onna-onna.nl

140 ms

logo.png

logo.png

186 ms

carchallenge-1.jpg

carchallenge-1.jpg

216 ms

rating-5.png

rating-5.png

187 ms

BitesWeLove-Goodiebag-e1459326429588.jpg

BitesWeLove-Goodiebag-e1459326429588.jpg

1435 ms

banner-website4-1.jpg

banner-website4-1.jpg

695 ms

klantvoordelen-homepage.jpg

klantvoordelen-homepage.jpg

480 ms

gtm.js

gtm.js

336 ms

li.png

li.png

192 ms

btn_berekenjepremie.png

btn_berekenjepremie.png

190 ms

bg-h2.png

bg-h2.png

313 ms

icon-onna.png

icon-onna.png

313 ms

logos_certifications.gif

logos_certifications.gif

280 ms

logo_eet.png

logo_eet.png

425 ms

logo_aegon.gif

logo_aegon.gif

425 ms

0Eihf_95vUTELNzQWn3Uh7G5VPa8gzse7OwlEhchJ_bff4nygsMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtgM.woff

0Eihf_95vUTELNzQWn3Uh7G5VPa8gzse7OwlEhchJ_bff4nygsMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtgM.woff

126 ms

AI7CtaXOKCDjvePW5kxLJQkRro0s4vdzPhOHbjEyK_Xff4RygsMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtM3.woff

AI7CtaXOKCDjvePW5kxLJQkRro0s4vdzPhOHbjEyK_Xff4RygsMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtM3.woff

224 ms

V7zPv1QDMW6FeQ8pH4n1NoMlMGGQCWrouhX-VSoMzs9ff4_ygsMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtg3.woff

V7zPv1QDMW6FeQ8pH4n1NoMlMGGQCWrouhX-VSoMzs9ff4_ygsMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtg3.woff

306 ms

2DAB8E_0_0.woff

2DAB8E_0_0.woff

535 ms

zXcR19vrlke-N4XcWdMTfWIrTG1ilI_HP_MeNOdM6KGff4zygsMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXt26.woff

zXcR19vrlke-N4XcWdMTfWIrTG1ilI_HP_MeNOdM6KGff4zygsMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXt26.woff

321 ms

i8Lj8sEbYocgRwQQRyw5p_XVMu7xaPtzFINvD7lTz1tff4xygsMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtIb.woff

i8Lj8sEbYocgRwQQRyw5p_XVMu7xaPtzFINvD7lTz1tff4xygsMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtIb.woff

320 ms

cse.js

cse.js

268 ms

arrow_sidebar.png

arrow_sidebar.png

410 ms

p.gif

p.gif

655 ms

conversion_async.js

conversion_async.js

391 ms

analytics.js

analytics.js

406 ms

activity;src=5139467;type=oo_ma0;cat=onnao0;u1=undefined;u2=undefined;ord=4214505637344

activity;src=5139467;type=oo_ma0;cat=onnao0;u1=undefined;u2=undefined;ord=4214505637344

268 ms

sdk.js

sdk.js

273 ms

fbds.js

fbds.js

314 ms

cse.js

cse.js

263 ms

jsapi

jsapi

48 ms

340 ms

default+nl.css

default+nl.css

26 ms

default+nl.I.js

default+nl.I.js

140 ms

376 ms

xd_arbiter.php

xd_arbiter.php

194 ms

171 ms

collect

collect

43 ms

default.css

default.css

23 ms

39 ms

async-ads.js

async-ads.js

97 ms

small-logo.png

small-logo.png

45 ms

76 ms

search_box_icon.png

search_box_icon.png

70 ms

clear.png

clear.png

70 ms

bg_search.png

bg_search.png

110 ms

SEO Factors

onna-onna.nl SEO score

0

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 Onna-onna.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 Onna-onna.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

onna-onna.nl

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