Tools & Wizards About Us
peha.at screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

peha.at

Home - peha.at

Page Load Speed

2.6 sec in total

First Response

479 ms

Resources Loaded

2 sec

Page Rendered

159 ms

peha.at screenshot

About Website

Click here to check amazing Peha content. Otherwise, check out these important facts you probably never knew about peha.at

PEHAMEDIEN ihr Spezialist in Sachen Druck, Werbung, Grafik, Austobeschriftung und Webdesign aus 4300 St. Valentin - Austria

Visit peha.at

Key Findings

We analyzed Peha.at page load time and found that the first response time was 479 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 45% of websites can load faster.

Performance Metrics

peha.at performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

peha.at

479 ms

main.css

130 ms

sidebar-main.css

273 ms

searchresultshighlight.js

275 ms

jquery.mousewheel-3.0.4.pack.js

246 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 82% of them (28 requests) were addressed to the original Peha.at, 6% (2 requests) were made to Staticxx.facebook.com and 3% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (997 ms) belongs to the original domain Peha.at.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Peha.at main page is 1.2 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. 30% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 18.0 kB

  • Original 24.3 kB
  • After minification 22.7 kB
  • After compression 6.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 18.0 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 9.2 kB

  • Original 1.0 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. Peha images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 84.0 kB

  • Original 106.2 kB
  • After minification 75.4 kB
  • After compression 22.2 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 84.0 kB or 79% of the original size.

CSS Optimization

-88%

Potential reduce by 52.7 kB

  • Original 59.8 kB
  • After minification 38.2 kB
  • After compression 7.1 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. Peha.at needs all CSS files to be minified and compressed as it can save up to 52.7 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (48%)

Requests Now

31

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

peha.at

peha.at

479 ms

main.css

main.css

130 ms

sidebar-main.css

sidebar-main.css

273 ms

searchresultshighlight.js

searchresultshighlight.js

275 ms

jquery.mousewheel-3.0.4.pack.js

jquery.mousewheel-3.0.4.pack.js

246 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

287 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

274 ms

frontend.css

frontend.css

282 ms

modernizr.min.js

modernizr.min.js

19 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

352 ms

jcarousel.responsive.js

jcarousel.responsive.js

376 ms

jquery.slicknav.js

jquery.slicknav.js

378 ms

cycle2.js

cycle2.js

385 ms

heading_headline.css

heading_headline.css

285 ms

format_headline.css

format_headline.css

284 ms

format_text.css

format_text.css

347 ms

jquery.min.js

jquery.min.js

8 ms

gradient.jpg

gradient.jpg

142 ms

1_56c2fad0deff9.jpg

1_56c2fad0deff9.jpg

946 ms

pic_3_543e7e1a58011.jpg

pic_3_543e7e1a58011.jpg

880 ms

pic_2_543e7994287a8.jpg

pic_2_543e7994287a8.jpg

751 ms

pic_8_543fc3b3878dd.jpg

pic_8_543fc3b3878dd.jpg

817 ms

pic_7_543d329096d27.jpg

pic_7_543d329096d27.jpg

782 ms

pic_4_543cee50a0191.jpg

pic_4_543cee50a0191.jpg

997 ms

sdk.js

sdk.js

68 ms

logo.png

logo.png

855 ms

arrow_left.png

arrow_left.png

884 ms

arrow_right.png

arrow_right.png

920 ms

shadow.jpg

shadow.jpg

961 ms

specialoffer.png

specialoffer.png

982 ms

vielfalt.jpg

vielfalt.jpg

993 ms

184 ms

xd_arbiter.php

xd_arbiter.php

71 ms

xd_arbiter.php

xd_arbiter.php

144 ms

Accessibility Review

peha.at accessibility score

76

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

peha.at 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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

peha.at SEO score

86

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

peha.at

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