Report Summary

  • 73

    Performance

    Renders faster than
    83% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

pacher.de

Home

Page Load Speed

2 sec in total

First Response

335 ms

Resources Loaded

1.4 sec

Page Rendered

303 ms

pacher.de screenshot

About Website

Welcome to pacher.de homepage info - get ready to check Pacher best content right away, or after learning these important things about pacher.de

Description

Visit pacher.de

Key Findings

We analyzed Pacher.de page load time and found that the first response time was 335 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 30% of websites can load faster.

Performance Metrics

pacher.de performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

Network Requests Diagram

pacher.de

335 ms

style.css

92 ms

style.responsive.css

180 ms

css

25 ms

jquery.js

308 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 81% of them (13 requests) were addressed to the original Pacher.de, 13% (2 requests) were made to Fonts.gstatic.com and 6% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (648 ms) belongs to the original domain Pacher.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 175.0 kB (20%)

Content Size

878.6 kB

After Optimization

703.7 kB

In fact, the total size of Pacher.de main page is 878.6 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 676.3 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 3.3 kB

  • Original 4.7 kB
  • After minification 4.0 kB
  • After compression 1.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 633 B, which is 14% 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 3.3 kB or 70% of the original size.

Image Optimization

-3%

Potential reduce by 23.1 kB

  • Original 676.3 kB
  • After minification 653.2 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. Pacher images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 102.6 kB

  • Original 144.9 kB
  • After minification 124.2 kB
  • After compression 42.3 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 102.6 kB or 71% of the original size.

CSS Optimization

-87%

Potential reduce by 46.0 kB

  • Original 52.8 kB
  • After minification 41.0 kB
  • After compression 6.7 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. Pacher.de needs all CSS files to be minified and compressed as it can save up to 46.0 kB or 87% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

13

After Optimization

13

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pacher. According to our analytics all requests are already optimized.

Accessibility Review

pacher.de accessibility score

68

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.

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

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

pacher.de 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

pacher.de 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

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

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