Tools & Wizards About Us
cor.to screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cor.to

Cor.to

Page Load Speed

2.8 sec in total

First Response

762 ms

Resources Loaded

1.9 sec

Page Rendered

131 ms

cor.to screenshot

About Website

Visit cor.to now to see the best up-to-date Cor content for Argentina and also check out these interesting facts you probably never knew about cor.to

Acortador argentino de urls. Rapido, simple y lindo. Ahorra caracteres y ten una presentacion mas elegante o linda de tu url. - Url shortener service. Fast, simple and nice. Save chars and have a nice...

Visit cor.to

Key Findings

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

Performance Metrics

cor.to performance score

0

Network Requests Diagram

cor.to

762 ms

screen.css

156 ms

jquery-1.6.1.js

664 ms

corto-ui.js

314 ms

bg-scissors-normal-clean.gif

308 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 89% of them (16 requests) were addressed to the original Cor.to, 11% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (762 ms) belongs to the original domain Cor.to.

Page Optimization Overview & Recommendations

Page size can be reduced by 81.8 kB (60%)

Content Size

137.2 kB

After Optimization

55.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Cor.to main page is 137.2 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. Only 10% of websites need less resources to load. Javascripts take 109.3 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 4.7 kB

  • Original 7.0 kB
  • After minification 6.1 kB
  • After compression 2.3 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 942 B, which is 13% 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 4.7 kB or 68% of the original size.

JavaScript Optimization

-55%

Potential reduce by 59.8 kB

  • Original 109.3 kB
  • After minification 109.1 kB
  • After compression 49.5 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 59.8 kB or 55% of the original size.

CSS Optimization

-82%

Potential reduce by 17.3 kB

  • Original 21.0 kB
  • After minification 15.3 kB
  • After compression 3.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. Cor.to needs all CSS files to be minified and compressed as it can save up to 17.3 kB or 82% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

17

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cor.to

cor.to

762 ms

screen.css

screen.css

156 ms

jquery-1.6.1.js

jquery-1.6.1.js

664 ms

corto-ui.js

corto-ui.js

314 ms

bg-scissors-normal-clean.gif

bg-scissors-normal-clean.gif

308 ms

bg-main.gif

bg-main.gif

157 ms

holder.gif

holder.gif

159 ms

mainlogo.gif

mainlogo.gif

314 ms

tab2.gif

tab2.gif

315 ms

tab1.gif

tab1.gif

317 ms

twitter-link-normal.gif

twitter-link-normal.gif

321 ms

button-up-english.gif

button-up-english.gif

331 ms

bloody-button-english.gif

bloody-button-english.gif

461 ms

button-hover-english.gif

button-hover-english.gif

475 ms

button-down-english.gif

button-down-english.gif

478 ms

twitter-link-hover-english.gif

twitter-link-hover-english.gif

473 ms

ga.js

ga.js

24 ms

__utm.gif

__utm.gif

24 ms

SEO Factors

cor.to SEO score

0

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 Cor.to 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 Cor.to 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

cor.to

Open Graph description is not detected on the main page of Cor. 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: