Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

trott.in

The best travel blogs your friends will actually read | Trottin

Page Load Speed

1.4 sec in total

First Response

84 ms

Resources Loaded

727 ms

Page Rendered

600 ms

trott.in screenshot

About Website

Visit trott.in now to see the best up-to-date Trott content for United States and also check out these interesting facts you probably never knew about trott.in

Trottin makes the best travel blogs, maps, and postcards that your friends will actually want to see. Travel tools as amazing as your adventures.

Visit trott.in

Key Findings

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

Performance Metrics

trott.in performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value5.2 s

75/100

10%

Network Requests Diagram

trott.in

84 ms

www.trottintravel.com

291 ms

bootstrap.min.css

107 ms

style.css

131 ms

frontend.css

152 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Trott.in, 38% (8 requests) were made to S3.amazonaws.com and 14% (3 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (345 ms) relates to the external source S3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 320.3 kB (19%)

Content Size

1.7 MB

After Optimization

1.4 MB

In fact, the total size of Trott.in main page is 1.7 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. 40% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 67.6 kB

  • Original 100.8 kB
  • After minification 98.4 kB
  • After compression 33.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 67.6 kB or 67% of the original size.

Image Optimization

-6%

Potential reduce by 79.6 kB

  • Original 1.3 MB
  • After minification 1.3 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. Trott images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 80.3 kB

  • Original 141.3 kB
  • After minification 141.3 kB
  • After compression 61.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 80.3 kB or 57% of the original size.

CSS Optimization

-83%

Potential reduce by 92.8 kB

  • Original 111.9 kB
  • After minification 108.3 kB
  • After compression 19.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. Trott.in needs all CSS files to be minified and compressed as it can save up to 92.8 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

17

After Optimization

9

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

Accessibility Review

trott.in accessibility score

85

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

trott.in best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

trott.in SEO score

92

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

Image elements do not have [alt] attributes

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 Trott.in 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 Trott.in 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 data is detected on the main page of Trott. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: