Tools & Wizards About Us
3.ly screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

3.ly

Create shrunken URLs - Shrunken.com

Page Load Speed

1.4 sec in total

First Response

316 ms

Resources Loaded

943 ms

Page Rendered

124 ms

3.ly screenshot

About Website

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

Create shrunken URLs from your longer website URLs. No registration required. Completely free to use.

Visit 3.ly

Key Findings

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

Performance Metrics

3.ly performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.087

93/100

15%

TTI (Time to Interactive)

Value8.0 s

42/100

10%

Network Requests Diagram

3.ly

316 ms

jquery.min.js

101 ms

3.jpg

281 ms

input_background.gif

186 ms

go.gif

186 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 50% of them (4 requests) were addressed to the original 3.ly, 25% (2 requests) were made to Google-analytics.com and 13% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (443 ms) relates to the external source Threely.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 27.2 kB (30%)

Content Size

90.0 kB

After Optimization

62.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of 3.ly main page is 90.0 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. Images take 56.2 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 12.1 kB

  • Original 16.6 kB
  • After minification 16.2 kB
  • After compression 4.5 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 12.1 kB or 73% of the original size.

Image Optimization

-27%

Potential reduce by 15.1 kB

  • Original 56.2 kB
  • After minification 41.1 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, 3 needs image optimization as it can save up to 15.1 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

We found no issues to fix!

Requests Now

6

After Optimization

6

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

3.ly

3.ly

316 ms

jquery.min.js

jquery.min.js

101 ms

3.jpg

3.jpg

281 ms

input_background.gif

input_background.gif

186 ms

go.gif

go.gif

186 ms

ga.js

ga.js

38 ms

__utm.gif

__utm.gif

11 ms

www.threely.com

www.threely.com

443 ms

Accessibility Review

3.ly accessibility score

83

Accessibility Issues

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

High

Form elements do not have associated labels

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

3.ly best practices score

67

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

Page has valid source maps

SEO Factors

3.ly SEO score

85

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

High

Page is blocked from indexing

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

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 3.ly 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 German language. Our system also found out that 3.ly 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

3.ly

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