Tools & Wizards About Us
status.si screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

status.si

Status.si - Izvirni pripomočki - Narejeno v Sloveniji - Vakuum

Page Load Speed

2.9 sec in total

First Response

287 ms

Resources Loaded

2.5 sec

Page Rendered

201 ms

status.si screenshot

About Website

Welcome to status.si homepage info - get ready to check Status best content for Slovenia right away, or after learning these important things about status.si

Status d.o.o. Metlika že več kot 27 let razvija in proizvaja inovativne pripomočke za pripravo in shranjevanje hrane. Kakovost na 1. mestu!

Visit status.si

Key Findings

We analyzed Status.si page load time and found that the first response time was 287 ms and then it took 2.7 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.si performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value22.2 s

0/100

10%

TBT (Total Blocking Time)

Value25,110 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value35.8 s

0/100

10%

Network Requests Diagram

status.si

287 ms

www.status.si

1325 ms

css

67 ms

043c66ea9946.css

256 ms

1ec6930d6c6e.css

230 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 87% of them (26 requests) were addressed to the original Status.si, 3% (1 request) were made to Fonts.googleapis.com and 3% (1 request) were made to Load.sumome.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Status.si.

Page Optimization Overview & Recommendations

Page size can be reduced by 638.5 kB (69%)

Content Size

925.3 kB

After Optimization

286.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Status.si main page is 925.3 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. 25% of websites need less resources to load. Images take 571.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 18.4 kB

  • Original 25.4 kB
  • After minification 23.0 kB
  • After compression 7.1 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 18.4 kB or 72% of the original size.

Image Optimization

-66%

Potential reduce by 379.8 kB

  • Original 571.9 kB
  • After minification 192.0 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 needs image optimization as it can save up to 379.8 kB or 66% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 148.4 kB

  • Original 226.5 kB
  • After minification 226.1 kB
  • After compression 78.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 148.4 kB or 66% of the original size.

CSS Optimization

-91%

Potential reduce by 91.9 kB

  • Original 101.5 kB
  • After minification 52.0 kB
  • After compression 9.6 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.si needs all CSS files to be minified and compressed as it can save up to 91.9 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (11%)

Requests Now

27

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

status.si

status.si

287 ms

www.status.si

www.status.si

1325 ms

css

css

67 ms

043c66ea9946.css

043c66ea9946.css

256 ms

1ec6930d6c6e.css

1ec6930d6c6e.css

230 ms

249 ms

load.sumome.com

load.sumome.com

482 ms

jquery.min.js

jquery.min.js

38 ms

d03f0e11a6ad.js

d03f0e11a6ad.js

415 ms

status-logo-2014.png

status-logo-2014.png

82 ms

sl.png

sl.png

172 ms

hr.png

hr.png

231 ms

en.png

en.png

171 ms

cart.gif

cart.gif

225 ms

icon-s986531e331.png

icon-s986531e331.png

246 ms

IMG_0042-2.jpg.940x486_q85_crop.jpg

IMG_0042-2.jpg.940x486_q85_crop.jpg

474 ms

untitled-9.jpg.940x486_q85_crop.jpg

untitled-9.jpg.940x486_q85_crop.jpg

253 ms

easytiler_4.jpg.940x486_q85_crop.jpg

easytiler_4.jpg.940x486_q85_crop.jpg

322 ms

IMG_0006__1.jpg.940x486_q85_crop.jpg

IMG_0006__1.jpg.940x486_q85_crop.jpg

297 ms

status-37_rdeca_nalepka-varijacija.jpg.300x0_q85_upscale.jpg

status-37_rdeca_nalepka-varijacija.jpg.300x0_q85_upscale.jpg

303 ms

status-8.jpg.300x0_q85_upscale.jpg

status-8.jpg.300x0_q85_upscale.jpg

320 ms

S_manjse_vrecke_11.JPG.300x0_q85_upscale.jpg

S_manjse_vrecke_11.JPG.300x0_q85_upscale.jpg

334 ms

IMG_0076-3.jpg.300x0_q85_upscale.jpg

IMG_0076-3.jpg.300x0_q85_upscale.jpg

379 ms

untitled-23_1.jpg.300x0_q85_upscale.jpg

untitled-23_1.jpg.300x0_q85_upscale.jpg

379 ms

recommendation-top.png

recommendation-top.png

395 ms

recommendation-bottom.png

recommendation-bottom.png

396 ms

IMG_0069-3_belo_drzalo_220x123.jpg.300x0_q85_upscale.jpg

IMG_0069-3_belo_drzalo_220x123.jpg.300x0_q85_upscale.jpg

414 ms

untitled-339_220x124.jpg.300x0_q85_upscale.jpg

untitled-339_220x124.jpg.300x0_q85_upscale.jpg

459 ms

bYbkq2nU2TSx4SwFbz5sCBa1RVmPjeKy21_GQJaLlJI.woff

bYbkq2nU2TSx4SwFbz5sCBa1RVmPjeKy21_GQJaLlJI.woff

30 ms

sprite_ac_normal.png

sprite_ac_normal.png

291 ms

Accessibility Review

status.si accessibility score

82

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

status.si best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

status.si SEO score

84

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    SL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Status.si can be misinterpreted by Google and other search engines. Our service has detected that Slovenian 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.si 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

status.si

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