Tools & Wizards About Us
intoto.nl screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

intoto.nl

InToto.nl ICT-partner voor de slimme ondernemer, gevestigd in Bunnik |

Page Load Speed

3.6 sec in total

First Response

350 ms

Resources Loaded

2.8 sec

Page Rendered

526 ms

intoto.nl screenshot

About Website

Welcome to intoto.nl homepage info - get ready to check In Toto best content right away, or after learning these important things about intoto.nl

InToto - ICT-partner voor de slimme ondernemer. Uw ICT partner uit Bunnik, omgeving Utrecht. InToto biedt alle diensten aan op het gebied van ICT.

Visit intoto.nl

Key Findings

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

intoto.nl performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.392

26/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

intoto.nl

350 ms

www.intoto.nl

540 ms

css

61 ms

css

74 ms

css

86 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 84% of them (37 requests) were addressed to the original Intoto.nl, 7% (3 requests) were made to Fonts.googleapis.com and 5% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Intoto.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 599.6 kB (26%)

Content Size

2.3 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intoto.nl main page is 2.3 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 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 55.3 kB

  • Original 66.2 kB
  • After minification 63.5 kB
  • After compression 10.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 55.3 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 59.7 kB

  • Original 1.6 MB
  • After minification 1.5 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. In Toto images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 274.2 kB

  • Original 407.6 kB
  • After minification 406.9 kB
  • After compression 133.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 274.2 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 210.4 kB

  • Original 245.8 kB
  • After minification 188.3 kB
  • After compression 35.3 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. Intoto.nl needs all CSS files to be minified and compressed as it can save up to 210.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (45%)

Requests Now

40

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intoto.nl

intoto.nl

350 ms

www.intoto.nl

www.intoto.nl

540 ms

css

css

61 ms

css

css

74 ms

css

css

86 ms

bootstrap.css

bootstrap.css

188 ms

font-awesome.css

font-awesome.css

245 ms

slick.css

slick.css

251 ms

style.css

style.css

254 ms

responsive.css

responsive.css

256 ms

settings.css

settings.css

277 ms

default.min.css

default.min.css

323 ms

jquery.js

jquery.js

509 ms

jquery-migrate.min.js

jquery-migrate.min.js

340 ms

jquery.easings.min.js

jquery.easings.min.js

343 ms

slick.min.js

slick.min.js

368 ms

mainscript.js

mainscript.js

401 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

537 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

607 ms

wp-embed.min.js

wp-embed.min.js

441 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

395 ms

ga.js

ga.js

19 ms

__utm.gif

__utm.gif

11 ms

logo_small.png

logo_small.png

264 ms

logo_desktop.png

logo_desktop.png

265 ms

dummy.png

dummy.png

264 ms

diensten_intoto.png

diensten_intoto.png

337 ms

cloud.png

cloud.png

264 ms

nsb.png

nsb.png

264 ms

voip.png

voip.png

338 ms

webdev.png

webdev.png

340 ms

hosting.png

hosting.png

342 ms

veepro1.png

veepro1.png

833 ms

datalekken.png

datalekken.png

770 ms

wordpress.png

wordpress.png

934 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

231 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

232 ms

teamfoto2.png

teamfoto2.png

1051 ms

loader.gif

loader.gif

175 ms

large_left.png

large_left.png

177 ms

large_right.png

large_right.png

284 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

666 ms

umbrella.png

umbrella.png

999 ms

umbrella_mobile.png

umbrella_mobile.png

576 ms

Accessibility Review

intoto.nl accessibility score

86

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

High

Links do not have a discernible name

Best Practices

intoto.nl best practices score

83

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

intoto.nl SEO score

91

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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

intoto.nl

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