Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

puckator.de

Großhandel Geschenke, Deko, Accessoires, Spielwaren & Trendartikel zu niedrigen Großhandelspreisen | Puckator DE

Page Load Speed

7.9 sec in total

First Response

724 ms

Resources Loaded

6.7 sec

Page Rendered

439 ms

puckator.de screenshot

About Website

Click here to check amazing Puckator content for Germany. Otherwise, check out these important facts you probably never knew about puckator.de

Top Lieferant & Importeur von Großhandel Geschenke, Deko, Trendartikel. Für Händler, Webshops, Museum- & Zooshops, Geschenkläden, Großhändler & Wiederverkäufer. 10% Rabatt für Neukunden. Registrieren ...

Visit puckator.de

Key Findings

We analyzed Puckator.de page load time and found that the first response time was 724 ms and then it took 7.2 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

puckator.de performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value30.4 s

0/100

10%

TBT (Total Blocking Time)

Value1,960 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.568

12/100

15%

TTI (Time to Interactive)

Value32.0 s

0/100

10%

Network Requests Diagram

www.puckator.de

724 ms

calendar.css

158 ms

styles-m.css

715 ms

styles.css

403 ms

payu.css

410 ms

Our browser made a total of 179 requests to load all elements on the main page. We found that 92% of them (164 requests) were addressed to the original Puckator.de, 4% (7 requests) were made to Use.typekit.net and 2% (4 requests) were made to Image.providesupport.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Puckator.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 510.8 kB (8%)

Content Size

6.8 MB

After Optimization

6.3 MB

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

HTML Optimization

-82%

Potential reduce by 137.2 kB

  • Original 166.3 kB
  • After minification 165.7 kB
  • After compression 29.1 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 137.2 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 367.5 kB

  • Original 6.5 MB
  • After minification 6.1 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. Puckator images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 269 B

  • Original 15.3 kB
  • After minification 15.3 kB
  • After compression 15.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 5.9 kB

  • Original 90.1 kB
  • After minification 86.1 kB
  • After compression 84.3 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. Puckator.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 136 (79%)

Requests Now

172

After Optimization

36

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

Accessibility Review

puckator.de accessibility score

83

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

puckator.de best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

puckator.de SEO score

73

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 doesn't use 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 Puckator.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 Puckator.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 Puckator. 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: