Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 69

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

tiny.pl

Tiny.pl - Skracanie linków. Zamień długi adres na krótki i łatwy!

Page Load Speed

2.2 sec in total

First Response

340 ms

Resources Loaded

1.7 sec

Page Rendered

108 ms

tiny.pl screenshot

About Website

Welcome to tiny.pl homepage info - get ready to check Tiny best content for Poland right away, or after learning these important things about tiny.pl

Darmowe skracanie adresĂłw URL.

Visit tiny.pl

Key Findings

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

Performance Metrics

tiny.pl performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value3,700 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.296

41/100

15%

TTI (Time to Interactive)

Value10.7 s

23/100

10%

Network Requests Diagram

tiny.pl

340 ms

jquery.min.js

247 ms

style.css

239 ms

cookieconsent.min.js

6 ms

adsbygoogle.js

5 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 16% of them (5 requests) were addressed to the original Tiny.pl, 16% (5 requests) were made to Pagead2.googlesyndication.com and 13% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (353 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.8 kB (41%)

Content Size

239.9 kB

After Optimization

142.1 kB

In fact, the total size of Tiny.pl main page is 239.9 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. 35% of websites need less resources to load. Javascripts take 197.5 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 13.2 kB

  • Original 19.5 kB
  • After minification 19.0 kB
  • After compression 6.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. 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 13.2 kB or 68% of the original size.

Image Optimization

-13%

Potential reduce by 1.7 kB

  • Original 13.7 kB
  • After minification 12.0 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. Obviously, Tiny needs image optimization as it can save up to 1.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-38%

Potential reduce by 75.8 kB

  • Original 197.5 kB
  • After minification 197.3 kB
  • After compression 121.7 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 75.8 kB or 38% of the original size.

CSS Optimization

-77%

Potential reduce by 7.1 kB

  • Original 9.2 kB
  • After minification 6.7 kB
  • After compression 2.1 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. Tiny.pl needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (38%)

Requests Now

29

After Optimization

18

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

Accessibility Review

tiny.pl accessibility score

86

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

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.

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

<frame> or <iframe> elements do not have a title

Best Practices

tiny.pl best practices score

69

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Uses deprecated APIs

SEO Factors

tiny.pl SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    PL

  • Language Claimed

    PL

  • Encoding

    ISO-8859-2

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tiny.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Tiny.pl main page’s claimed encoding is iso-8859-2. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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