Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    86% of websites

  • 77

    SEO

    Google-friendlier than
    45% of websites

Page Load Speed

678 ms in total

First Response

8 ms

Resources Loaded

270 ms

Page Rendered

400 ms

tr.im screenshot

About Website

Welcome to tr.im homepage info - get ready to check Tr best content for Vietnam right away, or after learning these important things about tr.im

Visit tr.im

Key Findings

We analyzed Tr.im page load time and found that the first response time was 8 ms and then it took 670 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

tr.im performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

92/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value5.1 s

76/100

10%

Network Requests Diagram

tr.im

8 ms

tr.im

50 ms

router.js

7 ms

routing

18 ms

32e202d.css

19 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 75% of them (21 requests) were addressed to the original Tr.im, 14% (4 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (88 ms) belongs to the original domain Tr.im.

Page Optimization Overview & Recommendations

Page size can be reduced by 879.3 kB (44%)

Content Size

2.0 MB

After Optimization

1.1 MB

In fact, the total size of Tr.im main page is 2.0 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. 50% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 5.6 kB

  • Original 8.2 kB
  • After minification 7.3 kB
  • After compression 2.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 5.6 kB or 69% of the original size.

Image Optimization

-35%

Potential reduce by 559.7 kB

  • Original 1.6 MB
  • After minification 1.0 MB

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, Tr needs image optimization as it can save up to 559.7 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 206.9 kB

  • Original 307.6 kB
  • After minification 284.9 kB
  • After compression 100.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 206.9 kB or 67% of the original size.

CSS Optimization

-89%

Potential reduce by 107.1 kB

  • Original 120.2 kB
  • After minification 91.6 kB
  • After compression 13.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. Tr.im needs all CSS files to be minified and compressed as it can save up to 107.1 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (18%)

Requests Now

22

After Optimization

18

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

Accessibility Review

tr.im accessibility score

81

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

Document doesn't have a <title> element

High

Links do not have a discernible name

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

tr.im 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

SEO Factors

tr.im SEO score

77

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tr.im can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Tr.im 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 Tr. 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: