3.7 sec in total
371 ms
3.1 sec
252 ms
Welcome to indi.nl homepage info - get ready to check INDI best content for Netherlands right away, or after learning these important things about indi.nl
Met meer dan 450.000 onderdelen van A-merken in elke branche zijn wij onderdeel van jouw oplossing. Zakelijke korting ✔ Nachtbezorging ✔ Specialistische kennis ✔
Visit indi.nlWe analyzed Indi.nl page load time and found that the first response time was 371 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 55% of websites can load faster.
indi.nl performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value12.1 s
0/100
25%
Value10.2 s
9/100
10%
Value2,470 ms
4/100
30%
Value0.006
100/100
15%
Value20.5 s
2/100
10%
371 ms
351 ms
352 ms
84 ms
84 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 80% of them (48 requests) were addressed to the original Indi.nl, 10% (6 requests) were made to Media.kramp.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (763 ms) belongs to the original domain Indi.nl.
Page size can be reduced by 1.1 MB (58%)
2.0 MB
835.0 kB
In fact, the total size of Indi.nl main page is 2.0 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. 45% of websites need less resources to load. Images take 688.8 kB which makes up the majority of the site volume.
Potential reduce by 362.8 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 362.8 kB or 93% of the original size.
Potential reduce by 87.7 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, INDI needs image optimization as it can save up to 87.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 344.9 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 344.9 kB or 70% of the original size.
Potential reduce by 338.9 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. Indi.nl needs all CSS files to be minified and compressed as it can save up to 338.9 kB or 85% of the original size.
Number of requests can be reduced by 8 (16%)
50
42
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INDI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
indi.nl
371 ms
www.indi.nl
351 ms
www.indi.nl
352 ms
84 ms
Default-Start
84 ms
Default-Start
341 ms
kor.min.js
459 ms
GetExternalizedStrings-Start
247 ms
base.min.css
249 ms
indi.css
422 ms
jquery.fancybox.css
249 ms
datepicker.css
261 ms
indi-extra-style.css
327 ms
gtm.js
100 ms
Wats-Request
150 ms
logo.png
225 ms
logo-indi-rwd.png
225 ms
Dutch_flag.png
92 ms
English_flag.png
92 ms
fontawesome-webfont.woff
332 ms
Y2C3bIBgbKJL_Ev85szdfKlL5K7um2o2
320 ms
bert-banner-homepage.png
296 ms
pijl-banner-homepage-wit.png
178 ms
welkom-nieuwe-website-690x397.jpg
292 ms
welkom-nieuwe-website-538x417.jpg
374 ms
TS2050E.jpg
317 ms
TS2050E.jpg
310 ms
090563MOT.jpg
380 ms
090563MOT.jpg
380 ms
27623.jpg
461 ms
27623.jpg
401 ms
ZRS6.jpg
398 ms
ZRS6.jpg
457 ms
TR76370BLA.jpg
463 ms
TR76370BLA.jpg
460 ms
EM83778.jpg
485 ms
EM83778.jpg
490 ms
302008TAY.jpg
626 ms
302008TAY.jpg
613 ms
ELEKTRODE_WP.jpg
549 ms
ELEKTRODE_WP.jpg
549 ms
PM0200.jpg
565 ms
PM0200.jpg
575 ms
PM130100.jpg
636 ms
PM130100.jpg
634 ms
5199356.jpg
649 ms
5199356.jpg
664 ms
daan-klantenservice.png
763 ms
Y2C3bIBgbKJL_EvV_ID258OGJMC3JMBLbDvgbKJLaIHd5d
301 ms
Y2C3bIBgbKJL_EvKb8OGfKlL5K7um2o2
307 ms
Y2C3bIBgbKJL_EvHbIhA5Ih2fKlL5K7um2o2
301 ms
Y2C3bIBgbKJL_Ev3bF535KvtbShAbFv2bEjq_F_
302 ms
Y2C3bIBgbKJL_EvGmFrgbhvgbKJLaIHd5d
301 ms
sprite.png
698 ms
analytics.js
109 ms
ajax-loader-small.gif
548 ms
ec.js
9 ms
collect
13 ms
collect
53 ms
ga-audiences
68 ms
indi.nl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
indi.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
indi.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 Indi.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 Indi.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.
indi.nl
Open Graph description is not detected on the main page of INDI. 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: