Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

corners.io

The domain name Corners.io is for sale

Page Load Speed

2.5 sec in total

First Response

188 ms

Resources Loaded

2 sec

Page Rendered

342 ms

corners.io screenshot

About Website

Visit corners.io now to see the best up-to-date Corners content and also check out these interesting facts you probably never knew about corners.io

The domain name Corners.io is for sale. Make an offer or buy it now at a set price.

Visit corners.io

Key Findings

We analyzed Corners.io page load time and found that the first response time was 188 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

corners.io performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value190 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

corners.io

188 ms

cornerssoon

154 ms

bt

202 ms

require.min.js

206 ms

main-r.min.js

227 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Corners.io, 78% (28 requests) were made to Static.parastorage.com and 8% (3 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (750 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (76%)

Content Size

2.5 MB

After Optimization

591.3 kB

In fact, the total size of Corners.io main page is 2.5 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. 70% of websites need less resources to load. Javascripts take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-38%

Potential reduce by 132 B

  • Original 343 B
  • After minification 296 B
  • After compression 211 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. This page needs HTML code to be minified as it can gain 47 B, which is 14% 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 132 B or 38% of the original size.

JavaScript Optimization

-76%

Potential reduce by 1.9 MB

  • Original 2.5 MB
  • After minification 2.5 MB
  • After compression 589.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 1.9 MB or 76% of the original size.

CSS Optimization

-77%

Potential reduce by 5.8 kB

  • Original 7.5 kB
  • After minification 6.0 kB
  • After compression 1.7 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. Corners.io needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (74%)

Requests Now

35

After Optimization

9

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

Accessibility Review

corners.io accessibility score

73

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

[aria-*] attributes do not match their roles

High

[aria-*] attributes do not have valid values

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

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

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

Links do not have a discernible name

Best Practices

corners.io 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

High

Page has valid source maps

SEO Factors

corners.io SEO score

93

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Corners.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Corners.io 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 Corners. 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: