Tools & Wizards About Us
polygon.us screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

polygon.us

About Polygonus / Digital art studio based in Medellin, Colombia

Page Load Speed

1.3 sec in total

First Response

49 ms

Resources Loaded

1.1 sec

Page Rendered

59 ms

polygon.us screenshot

About Website

Welcome to polygon.us homepage info - get ready to check Polygon best content for Colombia right away, or after learning these important things about polygon.us

Studio focused on digital art, design, 3D animation, visual and software development for the entertainment and collectibles industry.

Visit polygon.us

Key Findings

We analyzed Polygon.us page load time and found that the first response time was 49 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

polygon.us performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

www.polygon.us

49 ms

minified.js

49 ms

focus-within-polyfill.js

45 ms

polyfill.min.js

41 ms

lenis.min.js

85 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Polygon.us, 36% (17 requests) were made to Static.parastorage.com and 28% (13 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (489 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 565.0 kB (58%)

Content Size

966.6 kB

After Optimization

401.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Polygon.us main page is 966.6 kB. 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. HTML takes 676.4 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 560.7 kB

  • Original 676.4 kB
  • After minification 674.5 kB
  • After compression 115.7 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 560.7 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 18.7 kB
  • After minification 18.7 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. Polygon images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 4.3 kB

  • Original 271.5 kB
  • After minification 271.4 kB
  • After compression 267.2 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.

Requests Breakdown

Number of requests can be reduced by 13 (50%)

Requests Now

26

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.polygon.us

www.polygon.us

49 ms

minified.js

minified.js

49 ms

focus-within-polyfill.js

focus-within-polyfill.js

45 ms

polyfill.min.js

polyfill.min.js

41 ms

lenis.min.js

lenis.min.js

85 ms

8875.e26292eb.bundle.min.js

8875.e26292eb.bundle.min.js

38 ms

thunderbolt-commons.b7a35b00.bundle.min.js

thunderbolt-commons.b7a35b00.bundle.min.js

38 ms

main.d98de0fd.bundle.min.js

main.d98de0fd.bundle.min.js

74 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

75 ms

lodash.min.js

lodash.min.js

73 ms

react.production.min.js

react.production.min.js

74 ms

react-dom.production.min.js

react-dom.production.min.js

75 ms

browser-deprecation.bundle.es5.js

browser-deprecation.bundle.es5.js

74 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

75 ms

43a3c0_c71dc03782a143d1946fca63d96ad9cdf000.jpg

43a3c0_c71dc03782a143d1946fca63d96ad9cdf000.jpg

221 ms

bundle.min.js

bundle.min.js

54 ms

43a3c0_b8bff3924760437b9f0087a2924d7fccf000.jpg

43a3c0_b8bff3924760437b9f0087a2924d7fccf000.jpg

259 ms

82fcd3_8a0fc15348a8450d8b2be8f4807c2f75~mv2.jpg

82fcd3_8a0fc15348a8450d8b2be8f4807c2f75~mv2.jpg

479 ms

82fcd3_115ff98da7c640eeaba5ef057777f1f5~mv2.jpg

82fcd3_115ff98da7c640eeaba5ef057777f1f5~mv2.jpg

325 ms

82fcd3_39354cd2ceb743958b4082faaf059940~mv2.jpg

82fcd3_39354cd2ceb743958b4082faaf059940~mv2.jpg

258 ms

82fcd3_d1340474672a493288f373feaff89ed8~mv2.jpg

82fcd3_d1340474672a493288f373feaff89ed8~mv2.jpg

489 ms

82fcd3_1d6f964ae57e46199db88213aa337de5~mv2.jpg

82fcd3_1d6f964ae57e46199db88213aa337de5~mv2.jpg

435 ms

43a3c0_1a2afe7d59de4ea3aeff3e673b02cca2f000.jpg

43a3c0_1a2afe7d59de4ea3aeff3e673b02cca2f000.jpg

429 ms

90 ms

89 ms

89 ms

87 ms

85 ms

86 ms

128 ms

126 ms

123 ms

121 ms

119 ms

122 ms

file.woff

file.woff

137 ms

file.woff

file.woff

143 ms

file.woff

file.woff

155 ms

file.woff

file.woff

155 ms

file.woff

file.woff

156 ms

deprecation-es.v5.html

deprecation-es.v5.html

5 ms

bolt-performance

bolt-performance

17 ms

deprecation-style.v5.css

deprecation-style.v5.css

7 ms

right-arrow.svg

right-arrow.svg

13 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

5 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

5 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

4 ms

Accessibility Review

polygon.us accessibility score

98

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

Best Practices

polygon.us 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

polygon.us SEO score

100

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Polygon.us can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Polygon.us 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

polygon.us

Open Graph data is detected on the main page of Polygon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: