5.6 sec in total
563 ms
4.7 sec
285 ms
Welcome to iyyo.nl homepage info - get ready to check Iyyo best content right away, or after learning these important things about iyyo.nl
elektrisch vervoer elektrische bedrijfswagens
Visit iyyo.nlWe analyzed Iyyo.nl page load time and found that the first response time was 563 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
iyyo.nl performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value8.7 s
1/100
25%
Value7.4 s
27/100
10%
Value0 ms
100/100
30%
Value0.15
76/100
15%
Value4.4 s
83/100
10%
563 ms
326 ms
40 ms
330 ms
330 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 32% of them (15 requests) were addressed to the original Iyyo.nl, 43% (20 requests) were made to Strato-editor.com and 13% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Iyyo.nl.
Page size can be reduced by 436.6 kB (7%)
6.6 MB
6.2 MB
In fact, the total size of Iyyo.nl main page is 6.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. 65% of websites need less resources to load. Images take 6.1 MB which makes up the majority of the site volume.
Potential reduce by 24.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 24.4 kB or 77% of the original size.
Potential reduce by 89.2 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. Iyyo images are well optimized though.
Potential reduce by 242.2 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 242.2 kB or 66% of the original size.
Potential reduce by 80.7 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. Iyyo.nl needs all CSS files to be minified and compressed as it can save up to 80.7 kB or 84% of the original size.
Number of requests can be reduced by 25 (64%)
39
14
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iyyo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
iyyo.nl
563 ms
beng-proxy.js
326 ms
font-awesome.min.css
40 ms
popup-guistrap.css
330 ms
widget-runtime@3.76+sites31.3.css
330 ms
deploy@2.1.30+sites31.19.css
333 ms
slideshow-common@3.76+sites31.3.css
340 ms
jquery.js
681 ms
prototype.js
604 ms
jshelper.js
418 ms
url.js
419 ms
html.js
430 ms
prototype_impl.js
441 ms
widget-runtime@3.76+sites31.3.js
605 ms
slideshow-common@3.76+sites31.3.js
514 ms
main.css
529 ms
responsive.css
542 ms
fix_sidebar.js
608 ms
effects.js
628 ms
parallax.js
643 ms
font-awesome,version=4
533 ms
vars.css
241 ms
show.js
188 ms
css
16 ms
analytics.js
36 ms
Easy%20Go%20Electic%20logo%20PMS347%20%282%29.jpg
159 ms
rss_shiny_20.png
158 ms
style.css
254 ms
search.js
306 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
21 ms
Uxzkqj-MIMWle-XP2pDNAA.ttf
22 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
27 ms
7MygqTe2zs9YkP0adA9QQQ.ttf
26 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
26 ms
H1vB34nOKWXqzKotq25pcg.ttf
26 ms
fontawesome-webfont.woff
26 ms
collect
11 ms
_pixel.img
97 ms
arrows.png
101 ms
site-search.js
302 ms
iYYo%20800.jpg
1797 ms
dordrecht.JPG
3033 ms
Ev200%20BAK.jpg
951 ms
bus%201700.jpg
1044 ms
iYYo%20100%20personen%20en%20cargo%20ecomobiel.jpg
2675 ms
570.jpg
558 ms
iYYo_Star%20S%20BLANCO%20Foto%20met%20opdruk.jpg
830 ms
iyyo.nl accessibility score
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
iyyo.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
iyyo.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iyyo.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 Iyyo.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.
iyyo.nl
Open Graph description is not detected on the main page of Iyyo. 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: