4.3 sec in total
635 ms
3 sec
632 ms
Click here to check amazing Otto S content for Netherlands. Otherwise, check out these important facts you probably never knew about ottos.nl
Op zoek naar een partij die u volledig ontzorgt op het gebied van kantoor inrichting? | Otto’s biedt een totaaloplossing voor uw kantoor | Kantoor inrichters
Visit ottos.nlWe analyzed Ottos.nl page load time and found that the first response time was 635 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ottos.nl performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value10.8 s
0/100
25%
Value11.7 s
4/100
10%
Value1,710 ms
11/100
30%
Value0.001
100/100
15%
Value11.2 s
19/100
10%
635 ms
474 ms
194 ms
202 ms
197 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 65% of them (50 requests) were addressed to the original Ottos.nl, 19% (15 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Ottos.nl.
Page size can be reduced by 279.9 kB (10%)
2.9 MB
2.6 MB
In fact, the total size of Ottos.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. 70% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 140.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 140.6 kB or 84% of the original size.
Potential reduce by 139.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. Otto S images are well optimized though.
Potential reduce by 112 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 40 (69%)
58
18
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otto S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
ottos.nl
635 ms
4f95affe0f7e18dd7e8ea7227c4d5d9e.css
474 ms
post-5.css
194 ms
global.css
202 ms
post-4237.css
197 ms
post-9857.css
199 ms
post-9845.css
198 ms
css
21 ms
css
37 ms
css
38 ms
jquery.min.js
385 ms
jquery-migrate.min.js
296 ms
collect.js
51 ms
js
64 ms
js
103 ms
post-9223.css
208 ms
app.js
209 ms
frontend.js
211 ms
hoverIntent.min.js
309 ms
maxmegamenu.js
308 ms
forms.js
308 ms
webpack-pro.runtime.min.js
308 ms
webpack.runtime.min.js
568 ms
frontend-modules.min.js
570 ms
wp-polyfill-inert.min.js
569 ms
regenerator-runtime.min.js
568 ms
wp-polyfill.min.js
569 ms
hooks.min.js
572 ms
i18n.min.js
573 ms
frontend.min.js
573 ms
waypoints.min.js
573 ms
core.min.js
572 ms
frontend.min.js
574 ms
elements-handlers.min.js
614 ms
jet-elements.min.js
613 ms
underscore.min.js
639 ms
wp-util.min.js
640 ms
frontend.min.js
639 ms
lazyload.min.js
640 ms
recorder.js
280 ms
Richard-Rood-HR2-Otto-Kantoormeubelen-Anton-Rail-Infra-30-11-2022--scaled-e1689858462600.jpg
826 ms
Richard-Rood-HR2-Otto-Kantoormeubelen-Anton-Rail-Infra-30-11-2022-01813-scaled-e1689858444135.jpg
733 ms
%C2%A9Richard-Rood-HR2-Otto-Huize-Horeca-27-10-2023-03715-scaled.jpg
914 ms
background-home4.png
1829 ms
InHouseMaster_TX3000_EM_FINAL_PACK-2560x1707-1-e1669818039952.jpeg
650 ms
js
150 ms
analytics.js
52 ms
fa-regular-400.woff
126 ms
fa-solid-900.woff
313 ms
wARDj0u
7 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
123 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
31 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
202 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
97 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
232 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
232 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
121 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
231 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
231 ms
ping.js
218 ms
collect
129 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
146 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
168 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
168 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
168 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
168 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
168 ms
LogoOttos@2x.jpg
100 ms
1-1024x427.jpg
195 ms
1673426385231.jpeg
196 ms
Wij-ontzorgen.png
844 ms
De-Kaaz_A4A8513-1024x683.jpg
281 ms
%C2%A9Richard-Rood-HR2-Otto-Kantoormeubelen-Anton-Rail-Infra-30-11-2022-01813-1024x683.jpg
290 ms
%C2%A9Richard-Rood-HR2-Otto-Kantoormeubelen-Anton-Rail-Infra-30-11-2022-5-1024x683.jpg
473 ms
LogoOttos@2x_W.png
295 ms
ICON-FACEBOOK.png
295 ms
ICON-LINKEDIN.png
379 ms
ottos.nl accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
ottos.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
ottos.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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ottos.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 Ottos.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.
ottos.nl
Open Graph data is detected on the main page of Otto S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: