Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

pyrofex.com

Pyrotechnik Schickl Feuerwerke Pyro Schickl

Page Load Speed

2 sec in total

First Response

218 ms

Resources Loaded

1.6 sec

Page Rendered

187 ms

About Website

Click here to check amazing Pyro Fex content. Otherwise, check out these important facts you probably never knew about pyrofex.com

Pyrotechnik P. Schickl Mondsee - ein Feuerwerk fuer jeden Anlass

Visit pyrofex.com

Key Findings

We analyzed Pyrofex.com page load time and found that the first response time was 218 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

pyrofex.com performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

pyrofex.com

218 ms

www.pyrofex.com

261 ms

style.css

99 ms

topbg.gif

99 ms

clearpixel.gif

192 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 94% of them (48 requests) were addressed to the original Pyrofex.com, 4% (2 requests) were made to Ls1.wettercomassets.com and 2% (1 request) were made to Woys.wetter.com. The less responsive or slowest element that took the longest time to load (857 ms) belongs to the original domain Pyrofex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 33.4 kB (13%)

Content Size

248.1 kB

After Optimization

214.7 kB

In fact, the total size of Pyrofex.com main page is 248.1 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. Images take 223.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 17.9 kB

  • Original 23.1 kB
  • After minification 20.4 kB
  • After compression 5.2 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 2.7 kB, which is 12% 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 17.9 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 14.1 kB

  • Original 223.2 kB
  • After minification 209.1 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. Pyro Fex images are well optimized though.

CSS Optimization

-78%

Potential reduce by 1.5 kB

  • Original 1.9 kB
  • After minification 1.5 kB
  • After compression 407 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. Pyrofex.com needs all CSS files to be minified and compressed as it can save up to 1.5 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (76%)

Requests Now

49

After Optimization

12

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

Accessibility Review

pyrofex.com accessibility score

63

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

pyrofex.com best practices score

58

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

High

Serves images with low resolution

SEO Factors

pyrofex.com SEO score

67

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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