Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

tinyurl.com

URL Shortener, Branded Short Links & Analytics | TinyURL

Page Load Speed

520 ms in total

First Response

21 ms

Resources Loaded

498 ms

Page Rendered

1 ms

About Website

Click here to check amazing TinyURL content for United States. Otherwise, check out these important facts you probably never knew about tinyurl.com

Visit tinyurl.com

Key Findings

We analyzed Tinyurl.com page load time and found that the first response time was 21 ms and then it took 499 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

tinyurl.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value19.1 s

0/100

10%

TBT (Total Blocking Time)

Value8,320 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.121

84/100

15%

TTI (Time to Interactive)

Value45.5 s

0/100

10%

Network Requests Diagram

tinyurl.com

21 ms

app

181 ms

gtm.js

115 ms

js

148 ms

fbevents.js

36 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 47% of them (7 requests) were addressed to the original Tinyurl.com, 20% (3 requests) were made to Googletagmanager.com and 13% (2 requests) were made to A.pub.network. The less responsive or slowest element that took the longest time to load (222 ms) belongs to the original domain Tinyurl.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.4 kB (1%)

Content Size

1.3 MB

After Optimization

1.3 MB

In fact, the total size of Tinyurl.com main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 9.2 kB

  • Original 13.9 kB
  • After minification 12.1 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 1.8 kB, 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 9.2 kB or 66% of the original size.

JavaScript Optimization

-0%

Potential reduce by 85 B

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 1.2 MB

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.

CSS Optimization

-0%

Potential reduce by 105 B

  • Original 85.3 kB
  • After minification 85.3 kB
  • After compression 85.2 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. Tinyurl.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (62%)

Requests Now

13

After Optimization

5

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

Accessibility Review

tinyurl.com accessibility score

92

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

tinyurl.com 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

Missing source maps for large first-party JavaScript

SEO Factors

tinyurl.com SEO score

86

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

Links do not have descriptive text

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

    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 Tinyurl.com 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 Tinyurl.com 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 TinyURL. 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: