2.6 sec in total
322 ms
2 sec
246 ms
Welcome to otto.nl homepage info - get ready to check OTTO best content for Netherlands right away, or after learning these important things about otto.nl
OTTO: de online shop voor kleding, schoenen, meubels, elektronica en huishoudelijke apparaten. Direct online shoppen en in één keer of in termijnen betalen.
Visit otto.nlWe analyzed Otto.nl page load time and found that the first response time was 322 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
otto.nl performance score
name
value
score
weighting
Value6.8 s
1/100
10%
Value15.3 s
0/100
25%
Value12.5 s
3/100
10%
Value3,720 ms
1/100
30%
Value0.538
14/100
15%
Value21.8 s
1/100
10%
322 ms
485 ms
363 ms
186 ms
102 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 82% of them (32 requests) were addressed to the original Otto.nl, 8% (3 requests) were made to Tdn.r42tag.com and 5% (2 requests) were made to Dev.visualwebsiteoptimizer.com. The less responsive or slowest element that took the longest time to load (758 ms) belongs to the original domain Otto.nl.
Page size can be reduced by 1.4 MB (49%)
2.9 MB
1.5 MB
In fact, the total size of Otto.nl main page is 2.9 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 57.6 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 57.6 kB or 75% of the original size.
Potential reduce by 21.8 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. OTTO images are well optimized though.
Potential reduce by 683.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 683.3 kB or 72% of the original size.
Potential reduce by 652.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. Otto.nl needs all CSS files to be minified and compressed as it can save up to 652.3 kB or 84% of the original size.
Number of requests can be reduced by 8 (27%)
30
22
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OTTO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
otto.nl
322 ms
www.otto.nl
485 ms
styles.css
363 ms
picturefill.min.js
186 ms
require.js
102 ms
ishopevents.js
179 ms
1166-v1.js
120 ms
kortingcodeBG.png
94 ms
10014_DOB_jassen_KW9_FS16_FST_HP-min.jpg
261 ms
10015_WS_nieuwbinnen_KW9_FS16_FST_HP-min.jpg
427 ms
10016_HAKA_jeans_KW9_FS16_FST_HP-min.jpg
303 ms
newsletter-bonus-5.png
193 ms
5486_instagram.png
192 ms
5487_pinterest.png
193 ms
8273_Google%2B_icoon_otto.png
261 ms
5778_blog.png
263 ms
icon_myaccount.png
245 ms
icon-shop-cart130x94.png
326 ms
burgermenu_up.png
328 ms
iconsFooter.png
411 ms
OttoSans-Regular-131212.woff
297 ms
icomoon.woff
329 ms
ottobv_iconsweb.woff
380 ms
OttoSans-Bold-131212.woff
466 ms
fontawesome-webfont.woff
481 ms
OttoSansCond-Bold-131212.woff
420 ms
OttoSans-Thin-131212.woff
456 ms
app.js
758 ms
prod
43 ms
j.php
5 ms
analytics.js
26 ms
tag-permissions-c39757e6-8fb1-4730-bf97-75ce75ced294.js
47 ms
v.gif
23 ms
collect
23 ms
10025_DOB_badmode_KW9_FS16_SAT_HP_large_nieuwehoogte_2-min.jpg
363 ms
9939_MM_nieuwe_laptops_KW8_FS16_QST_HP-min.jpg
404 ms
9940_HH_nieuwe_koelkasten_KW8_FS16_QST_HP-min.jpg
356 ms
10017_SP_DVDW_KW9_FS16_HST_HP-min.jpg
443 ms
10018_KOB_crocs_KW7_FS16_QST_HP-min.jpg
454 ms
otto.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
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
otto.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
otto.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otto.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Otto.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.
otto.nl
Open Graph description is not detected on the main page of OTTO. 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: