Tools & Wizards About Us
st.org screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

st.org

Fackförbundet ST | För dig som jobbar inom staten eller på ett bolag

Page Load Speed

5.6 sec in total

First Response

467 ms

Resources Loaded

4.1 sec

Page Rendered

1 sec

st.org screenshot

About Website

Visit st.org now to see the best up-to-date ST content for Sweden and also check out these interesting facts you probably never knew about st.org

Fackförbundet ST är det största fackförbundet inom statlig verksamhet med över 99 000 medlemmar. Bli medlem i ST och få tillgång till råd och stöd samt en rad förmåner.

Visit st.org

Key Findings

We analyzed St.org page load time and found that the first response time was 467 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

st.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value3,150 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value31.6 s

0/100

10%

Network Requests Diagram

st.org

467 ms

www.st.org

1249 ms

c35dffef3db0a7b0.css

340 ms

c4e3e400-7caa2083e44f3377.js

746 ms

4705-483bf6c9441f38c3.js

659 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 97% of them (28 requests) were addressed to the original St.org, 3% (1 request) were made to Cdn.infisecure.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain St.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 225.4 kB (17%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images

In fact, the total size of St.org main page is 1.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. 25% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 187.7 kB

  • Original 228.0 kB
  • After minification 228.0 kB
  • After compression 40.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 187.7 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 37.7 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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. ST images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 19 (73%)

Requests Now

26

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ST. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

st.org

st.org

467 ms

www.st.org

www.st.org

1249 ms

c35dffef3db0a7b0.css

c35dffef3db0a7b0.css

340 ms

c4e3e400-7caa2083e44f3377.js

c4e3e400-7caa2083e44f3377.js

746 ms

4705-483bf6c9441f38c3.js

4705-483bf6c9441f38c3.js

659 ms

main-app-0367645b40285536.js

main-app-0367645b40285536.js

346 ms

7220-1f9be0fb7210a433.js

7220-1f9be0fb7210a433.js

557 ms

145-fbe05d69afc93f2c.js

145-fbe05d69afc93f2c.js

861 ms

3343-ed6518ecfa1c3015.js

3343-ed6518ecfa1c3015.js

467 ms

8618-378df76c3c05a3e3.js

8618-378df76c3c05a3e3.js

534 ms

3757-f98015859146dce9.js

3757-f98015859146dce9.js

795 ms

not-found-7b262e2190824230.js

not-found-7b262e2190824230.js

657 ms

global-error-7553a9ed3af5cc6f.js

global-error-7553a9ed3af5cc6f.js

679 ms

6171-454f18792fe8134d.js

6171-454f18792fe8134d.js

781 ms

layout-d6452488dd4279f7.js

layout-d6452488dd4279f7.js

781 ms

error-a6284865c0eb237e.js

error-a6284865c0eb237e.js

799 ms

3336-817d8e0bf7a7003e.js

3336-817d8e0bf7a7003e.js

864 ms

7837-5c0941447d7b1f2f.js

7837-5c0941447d7b1f2f.js

916 ms

3525-bd5aa4f5afa77750.js

3525-bd5aa4f5afa77750.js

904 ms

page-20cb359b3aab54bf.js

page-20cb359b3aab54bf.js

1018 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

1013 ms

webpack-b854d11221aeadad.js

webpack-b854d11221aeadad.js

659 ms

barracuda.js

barracuda.js

51 ms

bnith__aLVSnFnwyV5--UK757iDg66PuJwyaa4W7FN9PBXrGcOqiXVgOOQ1x6gZADbwSgdg

bnith__aLVSnFnwyV5--UK757iDg66PuJwyaa4W7FN9PBXrGcOqiXVgOOQ1x6gZADbwSgdg

2053 ms

image

image

246 ms

image

image

338 ms

image

image

143 ms

image

image

344 ms

image

image

140 ms

Accessibility Review

st.org accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

st.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

st.org SEO score

100

Search Engine Optimization Advices

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

    SV

  • Language Claimed

    SV

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise St.org can be misinterpreted by Google and other search engines. Our service has detected that Swedish is used on the page, and it matches the claimed language. Our system also found out that St.org 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.

Social Sharing Optimization

st.org

Open Graph data is detected on the main page of ST. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: