Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

fressnapf.de

Tierbedarf & Tiernahrung im Online-Shop | FRESSNAPF

Page Load Speed

8.4 sec in total

First Response

391 ms

Resources Loaded

7.8 sec

Page Rendered

181 ms

fressnapf.de screenshot

About Website

Visit fressnapf.de now to see the best up-to-date FRESSNAPF content for Germany and also check out these interesting facts you probably never knew about fressnapf.de

Bestelle jetzt online aus unserem umfangreichen Sortiment an Tierbedarf & Tiernahrung ✓ 12% für Erstbesteller ✓ große Auswahl ✓ Lieferung in 1-3 Werktagen.

Visit fressnapf.de

Key Findings

We analyzed Fressnapf.de page load time and found that the first response time was 391 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

fressnapf.de performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value2,800 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.18

67/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

fressnapf.de

391 ms

www.fressnapf.de

720 ms

jquery-2.1.1.min.js

382 ms

satelliteLib-0fbeaa74771ea1a95953017f769b3ab02f30455a.js

25 ms

jquery.colorbox-1.3.16.css

295 ms

Our browser made a total of 249 requests to load all elements on the main page. We found that 62% of them (154 requests) were addressed to the original Fressnapf.de, 7% (17 requests) were made to Go.flx1.com and 6% (16 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Ads.heias.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 507.0 kB (16%)

Content Size

3.2 MB

After Optimization

2.7 MB

In fact, the total size of Fressnapf.de main page is 3.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. 65% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 66.1 kB

  • Original 87.1 kB
  • After minification 81.2 kB
  • After compression 21.0 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 66.1 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 188.7 kB

  • Original 2.6 MB
  • After minification 2.4 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. FRESSNAPF images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 252.2 kB

  • Original 467.7 kB
  • After minification 461.1 kB
  • After compression 215.5 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 252.2 kB or 54% of the original size.

Requests Breakdown

Number of requests can be reduced by 158 (71%)

Requests Now

221

After Optimization

63

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

Accessibility Review

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

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.

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

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

fressnapf.de SEO score

88

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

High

Tap targets are not sized appropriately

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 Fressnapf.de 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 Fressnapf.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 FRESSNAPF. 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: