Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

toy-palace.de

Neu eingetroffen - Merchandise & Fanartikel Online Shop | Toy Palace

Page Load Speed

4.9 sec in total

First Response

655 ms

Resources Loaded

3.8 sec

Page Rendered

426 ms

toy-palace.de screenshot

About Website

Visit toy-palace.de now to see the best up-to-date Toy Palace content and also check out these interesting facts you probably never knew about toy-palace.de

Neu eingetroffen - Merchandise & Fanartikel für Star Wars, Movies, TV Serien, Comic & Animie. Das Neuste vom Neuen und exklusiv für Dich. Jetzt auf Lager. Hol Dir jetzt Dein Merchandise & Fanartikel!

Visit toy-palace.de

Key Findings

We analyzed Toy-palace.de page load time and found that the first response time was 655 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

toy-palace.de performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value2,170 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.737

6/100

15%

TTI (Time to Interactive)

Value21.9 s

1/100

10%

Network Requests Diagram

www.toy-palace.com

655 ms

css

64 ms

4d8a1a44c141b8992fc815435cf50e2d.1455521595.css

608 ms

ed2f8993ea0c43c503c2e70cbc4aaa3c.1455521493.js

896 ms

ga.js

16 ms

Our browser made a total of 195 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Toy-palace.de, 34% (67 requests) were made to Media.toy-palace.com and 6% (12 requests) were made to Cdn.toy-palace.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Media.toy-palace.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (25%)

Content Size

5.2 MB

After Optimization

3.9 MB

In fact, the total size of Toy-palace.de main page is 5.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 200.2 kB

  • Original 225.7 kB
  • After minification 188.4 kB
  • After compression 25.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 37.3 kB, which is 17% 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 200.2 kB or 89% of the original size.

Image Optimization

-4%

Potential reduce by 136.5 kB

  • Original 3.7 MB
  • After minification 3.6 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. Toy Palace images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 654.1 kB

  • Original 854.0 kB
  • After minification 697.5 kB
  • After compression 199.9 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 654.1 kB or 77% of the original size.

CSS Optimization

-87%

Potential reduce by 324.7 kB

  • Original 374.8 kB
  • After minification 298.8 kB
  • After compression 50.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. Toy-palace.de needs all CSS files to be minified and compressed as it can save up to 324.7 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (10%)

Requests Now

186

After Optimization

168

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

Accessibility Review

toy-palace.de accessibility score

78

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

[id] attributes on active, focusable elements are not unique

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

toy-palace.de best practices score

67

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

toy-palace.de SEO score

84

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

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 Toy-palace.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 Toy-palace.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 Toy Palace. 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: