3.2 sec in total
619 ms
2.4 sec
110 ms
Click here to check amazing Status Netstream content for Switzerland. Otherwise, check out these important facts you probably never knew about status.netstream.ch
Welcome to Netstream Status's home for real-time and historical data on system performance.
Visit status.netstream.chWe analyzed Status.netstream.ch page load time and found that the first response time was 619 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
status.netstream.ch performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value13.7 s
0/100
25%
Value6.2 s
43/100
10%
Value830 ms
35/100
30%
Value0.209
60/100
15%
Value11.6 s
18/100
10%
619 ms
700 ms
542 ms
306 ms
245 ms
Our browser made a total of 25 requests to load all elements on the main page. We found that 88% of them (22 requests) were addressed to the original Status.netstream.ch, 4% (1 request) were made to D31qbv1cthcecs.cloudfront.net and 4% (1 request) were made to D5nxst8fruw4z.cloudfront.net. The less responsive or slowest element that took the longest time to load (700 ms) belongs to the original domain Status.netstream.ch.
Page size can be reduced by 123.9 kB (67%)
185.0 kB
61.1 kB
In fact, the total size of Status.netstream.ch main page is 185.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. Javascripts take 127.2 kB which makes up the majority of the site volume.
Potential reduce by 16.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 5.8 kB, which is 29% 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 16.6 kB or 84% of the original size.
Potential reduce by 3.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. Obviously, Status Netstream needs image optimization as it can save up to 3.8 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 86.4 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 86.4 kB or 68% of the original size.
Potential reduce by 17.1 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. Status.netstream.ch needs all CSS files to be minified and compressed as it can save up to 17.1 kB or 78% of the original size.
Number of requests can be reduced by 8 (38%)
21
13
The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Status Netstream. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
status.netstream.ch
619 ms
juice
700 ms
style.css
542 ms
accordion.css
306 ms
style_Help.css
245 ms
style_Support.css
249 ms
jquery-1.4.2.min.js
655 ms
jquery-ui-1.8rc2.custom.min.js
669 ms
jquery.plugins.js
346 ms
easyTooltip.js
484 ms
swfobject.js
685 ms
bg_gradient.png
242 ms
logo_netstream.png
144 ms
transp.gif
145 ms
icon_nws_0.png
145 ms
icon_zoom.png
143 ms
icon_nws_1.png
144 ms
atrk.js
29 ms
feed_small.gif
257 ms
icon_intlink.png
256 ms
arrow_netstream.png
356 ms
atrk.gif
22 ms
test.png
463 ms
print.css
137 ms
handheld.css
142 ms
status.netstream.ch 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.
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.
status.netstream.ch 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
status.netstream.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Status.netstream.ch 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 Status.netstream.ch main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
status.netstream.ch
Open Graph description is not detected on the main page of Status Netstream. 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: