Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

storum.eu

Градинска техника и градински уреди | GardenMax

Page Load Speed

2.6 sec in total

First Response

358 ms

Resources Loaded

1.6 sec

Page Rendered

665 ms

storum.eu screenshot

About Website

Welcome to storum.eu homepage info - get ready to check Storum best content for Bulgaria right away, or after learning these important things about storum.eu

Вземете сега градинска техника и градински уреди на изгодни цени. Разнообразие от марки, с доказан произход от GardenMax.

Visit storum.eu

Key Findings

We analyzed Storum.eu page load time and found that the first response time was 358 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

storum.eu performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value60.9 s

0/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.476

18/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

storum.eu

358 ms

style.css

227 ms

menu.css

179 ms

mootools-1.2.5-core.js

252 ms

mootools-1.2.2.2-more.js

250 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 85% of them (55 requests) were addressed to the original Storum.eu, 11% (7 requests) were made to Static.xx.fbcdn.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (841 ms) belongs to the original domain Storum.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 996.1 kB (11%)

Content Size

8.9 MB

After Optimization

7.9 MB

In fact, the total size of Storum.eu main page is 8.9 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. 50% of websites need less resources to load. Images take 8.5 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 89.1 kB

  • Original 100.4 kB
  • After minification 52.4 kB
  • After compression 11.4 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 48.1 kB, which is 48% 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 89.1 kB or 89% of the original size.

Image Optimization

-8%

Potential reduce by 691.0 kB

  • Original 8.5 MB
  • After minification 7.8 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. Storum images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 178.9 kB

  • Original 255.7 kB
  • After minification 245.2 kB
  • After compression 76.8 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 178.9 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 37.1 kB

  • Original 44.6 kB
  • After minification 38.6 kB
  • After compression 7.5 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. Storum.eu needs all CSS files to be minified and compressed as it can save up to 37.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (36%)

Requests Now

64

After Optimization

41

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

Accessibility Review

storum.eu accessibility score

64

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

storum.eu best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

storum.eu 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

    BG

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

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