3.1 sec in total
98 ms
2.7 sec
358 ms
Visit upstairs.nl now to see the best up-to-date Upstairs content and also check out these interesting facts you probably never knew about upstairs.nl
Wij denken graag met je mee over de traprenovatie van jouw trap, zodat die perfect aansluit bij jouw interieur. Neem contact met ons op.
Visit upstairs.nlWe analyzed Upstairs.nl page load time and found that the first response time was 98 ms and then it took 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.
upstairs.nl performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value12.7 s
0/100
25%
Value12.1 s
3/100
10%
Value3,730 ms
1/100
30%
Value0.027
100/100
15%
Value21.4 s
1/100
10%
98 ms
84 ms
164 ms
166 ms
9 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Upstairs.nl, 5% (4 requests) were made to Platform.twitter.com and 3% (3 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (724 ms) relates to the external source Upstairs.com.
Page size can be reduced by 958.6 kB (41%)
2.3 MB
1.4 MB
In fact, the total size of Upstairs.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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 62.3 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 62.3 kB or 80% of the original size.
Potential reduce by 16.3 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. Upstairs images are well optimized though.
Potential reduce by 504.1 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 504.1 kB or 68% of the original size.
Potential reduce by 375.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. Upstairs.nl needs all CSS files to be minified and compressed as it can save up to 375.9 kB or 84% of the original size.
Number of requests can be reduced by 49 (59%)
83
34
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Upstairs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
98 ms
language-selector.css
84 ms
advanced-responsive-video-embedder-public.css
164 ms
style.css
166 ms
font-awesome.css
9 ms
bootstrap.no-responsive.no-icons.min.css
9 ms
bootstrap-responsive.css
164 ms
flexslider.css
166 ms
slick.css
173 ms
mediaelementplayer.min.css
175 ms
engine.css
244 ms
style.css
248 ms
style-cms.css
254 ms
responsive.css
244 ms
jquery.fancybox-1.3.7.min.css
260 ms
wpgmza_style.css
262 ms
M9bPKixNLarUMYYydHMz04sSS1L1cjPzdAz1ywt0s0rKU1NLivWzgAjCBAA.js
482 ms
formreset.min.css
326 ms
formsmain.min.css
330 ms
readyclass.min.css
331 ms
browsers.min.css
347 ms
M9FPzs_NTc0r0S1KLcip1MvNzAMA.js
349 ms
bootstrap.min.js
4 ms
hZBtDoIwDEAvJIwrFVpmsduw3RRuLwQTjSL-adK-14-0cWW0DKzmwIyyucFcLzSZMJKemi--gO6yxTpwfDeEWwWdXSBkqEaBmXRLSChQzBVEfNY_e1_bh2shneue843RDh0O4MkkARL-HTh0oKkYyb5lZ8B0b9O0j0fwHP0PJmWBx6f69Z8P.js
569 ms
DcIBCsAgDAPAH9l9qawRIpsT0_7fHXdZLaVzy1xCysb_9v2V8LSaLyc7EQ3BRBw.js
411 ms
M9AvLSguScwsKtZPLC5OLSnWzyrWz8zLLNExwCaTVV6Qk1iZWoRdNjUvPTMvFQA.js
581 ms
dY5bDgIxCEU3JG0aP1wPVhwZ-7K0o929mDhOovEP7j2c4Kxwo1JJBGIPjQOnqWMAH8VqamfZiJ2zU8WF24BzrlHg1Etgj41A-4VS45xW5IvYALUQiiow-XHMD_sZ5lunOsy6gzN7czCRf0_epIb6rinor_-QmLvQ_UIUXqIn.js
435 ms
conversion.js
15 ms
wp-emoji-release.min.js
351 ms
analytics.js
4 ms
collect
38 ms
collect
57 ms
hotjar-36782.js
199 ms
de.png
196 ms
en.png
194 ms
be.png
195 ms
nl.png
193 ms
Upstairs-logo-nieuws.png
247 ms
trapstijltest_header12.jpg
396 ms
slider_shadygrey.jpg
424 ms
Upstairs-bedrijfsfilm1.jpg
419 ms
slider_homepage.jpg
547 ms
homepage_vtwonen.jpg
368 ms
bertrambeerbaum21.jpg
448 ms
123-Eindhoven-e1417429707354.jpg
664 ms
slider_SolidBlack.jpg
558 ms
Teaser-Mississippi-Pine.jpg
575 ms
slider_stoerchique.jpg
577 ms
aanvraag-button.png
528 ms
all.js
90 ms
overlay.png
619 ms
656 ms
teaserButtons.png
654 ms
teaserDescription.png
654 ms
frutiger-cn_0-webfont.woff
640 ms
widgets.js
158 ms
headerBg.png
665 ms
cbw_new.png
724 ms
1755.js
34 ms
172 ms
f.jsonp
598 ms
UpstairsTraprenovatie
294 ms
86 ms
teaserButton_right.png
555 ms
loader-small.gif
554 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
157 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
67 ms
86 ms
xd_arbiter.php
98 ms
xd_arbiter.php
162 ms
90 ms
84 ms
syndication
88 ms
344772774004420608
122 ms
feed
509 ms
visit-data
210 ms
proxy.jpg
32 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
41 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
80 ms
d41b550956725342d9330ea39cfe0d20_normal.png
91 ms
CdMmmB0XIAAxV0P.jpg
89 ms
CdMmxmNWIAASeG3.jpg
93 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
88 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
90 ms
4.png
84 ms
5.png
89 ms
3.png
85 ms
proxy.jpg
4 ms
upstairs.nl accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
upstairs.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
upstairs.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Upstairs.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 Upstairs.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.
upstairs.nl
Open Graph data is detected on the main page of Upstairs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: