Report Summary

  • 56

    Performance

    Renders faster than
    73% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

trolli.de

Trolli

Page Load Speed

4.7 sec in total

First Response

898 ms

Resources Loaded

3.3 sec

Page Rendered

534 ms

trolli.de screenshot

About Website

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

Entdecke die verrückten Fruchtgummis von Trolli. Mit dabei natürlich unsere Klassiker: Trolli Burger, Apfelringe, saure Glühwürmchen, Playmouse und Milch Kuh

Visit trolli.de

Key Findings

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

Performance Metrics

trolli.de performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

www.trolli.de

898 ms

wp-emoji-release.min.js

101 ms

bootstrap.css

305 ms

front.css

196 ms

trolli-de.css

296 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 96% of them (51 requests) were addressed to the original Trolli.de, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (959 ms) belongs to the original domain Trolli.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 537.7 kB (28%)

Content Size

1.9 MB

After Optimization

1.4 MB

In fact, the total size of Trolli.de main page is 1.9 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 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 43.9 kB

  • Original 53.4 kB
  • After minification 48.2 kB
  • After compression 9.5 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 43.9 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 23.2 kB

  • Original 1.2 MB
  • After minification 1.2 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. Trolli images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 204.1 kB

  • Original 300.0 kB
  • After minification 292.8 kB
  • After compression 95.8 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 204.1 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 266.5 kB

  • Original 314.9 kB
  • After minification 273.8 kB
  • After compression 48.4 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. Trolli.de needs all CSS files to be minified and compressed as it can save up to 266.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (40%)

Requests Now

48

After Optimization

29

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

Accessibility Review

trolli.de accessibility score

69

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

Image elements do not have [alt] attributes

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

trolli.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

trolli.de SEO score

79

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 Trolli.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 Trolli.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 Trolli. 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: