7.3 sec in total
600 ms
6.4 sec
338 ms
Click here to check amazing Screens R Us content. Otherwise, check out these important facts you probably never knew about screensrus.co.nz
Welcome to Screens R Us where we provide quality NZ made security and screen doors. Contact us for a free measure and quote for your Auckland home.
Visit screensrus.co.nzWe analyzed Screensrus.co.nz page load time and found that the first response time was 600 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
screensrus.co.nz performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value13.7 s
0/100
25%
Value14.8 s
1/100
10%
Value550 ms
53/100
30%
Value0.086
93/100
15%
Value12.3 s
15/100
10%
600 ms
600 ms
859 ms
45 ms
54 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 60% of them (42 requests) were addressed to the original Screensrus.co.nz, 13% (9 requests) were made to Blueoceancdn143.blob.core.windows.net and 9% (6 requests) were made to Ajax.aspnetcdn.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Blueoceancdn143.blob.core.windows.net.
Page size can be reduced by 231.5 kB (5%)
5.0 MB
4.7 MB
In fact, the total size of Screensrus.co.nz main page is 5.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. 55% of websites need less resources to load. Images take 4.7 MB which makes up the majority of the site volume.
Potential reduce by 33.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. This page needs HTML code to be minified as it can gain 10.9 kB, which is 26% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 33.6 kB or 81% of the original size.
Potential reduce by 160.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. Screens R Us images are well optimized though.
Potential reduce by 24.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 24.9 kB or 17% of the original size.
Potential reduce by 12.8 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. Screensrus.co.nz needs all CSS files to be minified and compressed as it can save up to 12.8 kB or 34% of the original size.
Number of requests can be reduced by 24 (44%)
55
31
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Screens R Us. 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 8 to 1 for CSS and as a result speed up the page load time.
screensrus.co.nz
600 ms
www.screensrus.co.nz
600 ms
www.screensrus.co.nz
859 ms
bootstrap.min.css
45 ms
slick.css
54 ms
animate.min.css
68 ms
lightbox.css
214 ms
rte.css
408 ms
style.css
626 ms
alert.css
763 ms
jquery-2.1.1.min.js
52 ms
jquery.validate.min.js
50 ms
jquery.validate.unobtrusive.min.js
51 ms
f9e439cac3f1001bd0cbe2c.js
422 ms
umbracoforms-dependencies.js
820 ms
umbracoforms.js
819 ms
umbracoforms-conditions.js
819 ms
jquery-1.12.4.min.js
51 ms
bootstrap.min.js
50 ms
slick.min.js
52 ms
lightbox.js
837 ms
animate.js
837 ms
grid.js
982 ms
misc.js
984 ms
css
27 ms
analytics.js
71 ms
gtm.js
116 ms
close.png
311 ms
loading.gif
310 ms
prev.png
311 ms
next.png
311 ms
logo.jpg
367 ms
email-red.png
375 ms
phone.png
394 ms
hero.jpg
609 ms
amplimesh_pointer_window_1lr.jpg
638 ms
amplimesh_clearguard_door_21lr.jpg
649 ms
amplimesh_pointer_door_2lr.jpg
776 ms
arrow-right-thin.png
568 ms
entry-level-screen.jpg
796 ms
img_7218.jpg
847 ms
hi_screen_expansion_cropped.jpg
884 ms
content-1.jpg
1232 ms
content-2.jpg
1469 ms
img_7119-2.jpg
1054 ms
hinged-insect-screen.jpg
1073 ms
grey-dotted-bg.png
1426 ms
clearguard_handle_1lr.jpg
2398 ms
globe.png
1625 ms
blob-gallery.png
1266 ms
gallery-image.jpg
1441 ms
blob-newsletter.png
1459 ms
blob-contact.png
1586 ms
arrow-up.png
1600 ms
facebook.png
1617 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWkANDP.woff
41 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduh8MKkANDP.woff
53 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhycKkANDP.woff
63 ms
collect
16 ms
js
56 ms
js
99 ms
0470277974031133a82282247a82698ea05be369.jpg
2433 ms
3159c3b203fa5f4709639291249522c45ac4ea55.jpg
2897 ms
a8950e6ef137b2569f21ff37218c682e5f80a98b.jpg
2851 ms
aee69f08f061eaaf37449a6ed4955058328528c6.jpg
1544 ms
e094af40dc6857b732294ddccafd474e0aad78ae.jpg
1510 ms
90c12b6e6a7ff10ddf8459c4032041d419b13732.jpg
1505 ms
1500df0831cf6f9506c769a142defe7abe45b287.jpg
1856 ms
b218122b1d3f87b31c0f9de969a4c196de01ab22.jpg
2144 ms
0140bdc3809c7849e1a1c8a3ac7d7a22f5979fcd.jpg
1922 ms
screensrus.co.nz 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.
ARIA toggle fields do not have accessible names
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
screensrus.co.nz 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
screensrus.co.nz 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Screensrus.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English 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 Screensrus.co.nz 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.
screensrus.co.nz
Open Graph description is not detected on the main page of Screens R Us. 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: