Report Summary

  • 0

    Performance

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

Page Load Speed

1.2 sec in total

First Response

331 ms

Resources Loaded

774 ms

Page Rendered

102 ms

polygonal.de screenshot

About Website

Click here to check amazing Polygonal content for United States. Otherwise, check out these important facts you probably never knew about polygonal.de

Visit polygonal.de

Key Findings

We analyzed Polygonal.de page load time and found that the first response time was 331 ms and then it took 876 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

polygonal.de performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

polygonal.de

331 ms

polygonal.js

399 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Polygonal.de and no external sources were called. The less responsive or slowest element that took the longest time to load (399 ms) belongs to the original domain Polygonal.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 171.0 kB (45%)

Content Size

383.6 kB

After Optimization

212.7 kB

In fact, the total size of Polygonal.de main page is 383.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 221.3 kB which makes up the majority of the site volume.

HTML Optimization

-47%

Potential reduce by 389 B

  • Original 822 B
  • After minification 813 B
  • After compression 433 B

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 389 B or 47% of the original size.

Image Optimization

-1%

Potential reduce by 1.5 kB

  • Original 147.4 kB
  • After minification 145.9 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. Polygonal images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 159.0 kB

  • Original 221.3 kB
  • After minification 188.0 kB
  • After compression 62.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 159.0 kB or 72% of the original size.

CSS Optimization

-71%

Potential reduce by 10.1 kB

  • Original 14.1 kB
  • After minification 10.3 kB
  • After compression 4.0 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. Polygonal.de needs all CSS files to be minified and compressed as it can save up to 10.1 kB or 71% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

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

Accessibility Review

polygonal.de accessibility score

55

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

Document doesn't have a <title> element

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

polygonal.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

polygonal.de SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Polygonal.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Polygonal.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 Polygonal. 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: