Report Summary

  • 79

    Performance

    Renders faster than
    86% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    86% of websites

  • 92

    SEO

    Google-friendlier than
    79% of websites

status.st

status.st

Page Load Speed

3.5 sec in total

First Response

508 ms

Resources Loaded

2.3 sec

Page Rendered

702 ms

status.st screenshot

About Website

Welcome to status.st homepage info - get ready to check St Atus best content for Sweden right away, or after learning these important things about status.st

This domain may be for sale!

Visit status.st

Key Findings

We analyzed Status.st page load time and found that the first response time was 508 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

status.st performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value2.8 s

95/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.272

45/100

15%

TTI (Time to Interactive)

Value3.0 s

95/100

10%

Network Requests Diagram

status.st

508 ms

1127 ms

SpryMenuBar.js

438 ms

SpryMenuBarHorizontal.css

329 ms

1%20Statuslogo.gif

140 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Status.st, 86% (18 requests) were made to Privat.bahnhof.se and 5% (1 request) were made to Statcounter.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Privat.bahnhof.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.9 kB (76%)

Content Size

50.2 kB

After Optimization

12.3 kB

In fact, the total size of Status.st main page is 50.2 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. 15% of websites need less resources to load. Javascripts take 44.6 kB which makes up the majority of the site volume.

HTML Optimization

-39%

Potential reduce by 128 B

  • Original 326 B
  • After minification 320 B
  • After compression 198 B

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 128 B or 39% of the original size.

JavaScript Optimization

-74%

Potential reduce by 33.0 kB

  • Original 44.6 kB
  • After minification 37.0 kB
  • After compression 11.6 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 33.0 kB or 74% of the original size.

CSS Optimization

-90%

Potential reduce by 4.8 kB

  • Original 5.3 kB
  • After minification 1.8 kB
  • After compression 511 B

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.st needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 90% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

20

After Optimization

20

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of St Atus. According to our analytics all requests are already optimized.

Accessibility Review

status.st accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

Best Practices

status.st best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

status.st SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Status.st 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.st 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of St Atus. 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: