Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

trip.ee

Trip.ee | Eesti reisiportaal

Page Load Speed

1.9 sec in total

First Response

32 ms

Resources Loaded

1.4 sec

Page Rendered

474 ms

About Website

Welcome to trip.ee homepage info - get ready to check Trip best content for Estonia right away, or after learning these important things about trip.ee

Trip.ee koondab kokku kõik reisimiseks vajaliku: reisijate kogemused ja reisisoovitused, reisiideed, odavad piletid, reisikaaslaste otsingu ja reisivarustuse ost ja müük

Visit trip.ee

Key Findings

We analyzed Trip.ee page load time and found that the first response time was 32 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 40% of websites can load faster.

Performance Metrics

trip.ee performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value4.4 s

73/100

10%

TBT (Total Blocking Time)

Value1,460 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value9.7 s

28/100

10%

Network Requests Diagram

trip.ee

32 ms

trip.ee

458 ms

gpt.js

114 ms

script.js

418 ms

86fa9010f2f3ec25.css

30 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 59% of them (23 requests) were addressed to the original Trip.ee, 33% (13 requests) were made to Trip3spaces.fra1.cdn.digitaloceanspaces.com and 5% (2 requests) were made to Securepubads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (555 ms) belongs to the original domain Trip.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 144.8 kB (21%)

Content Size

679.6 kB

After Optimization

534.8 kB

In fact, the total size of Trip.ee main page is 679.6 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. 45% of websites need less resources to load. Images take 333.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 63.1 kB

  • Original 78.4 kB
  • After minification 78.2 kB
  • After compression 15.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 63.1 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 6.7 kB

  • Original 333.4 kB
  • After minification 326.7 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. Trip images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 74.9 kB

  • Original 267.7 kB
  • After minification 267.7 kB
  • After compression 192.8 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 74.9 kB or 28% of the original size.

Requests Breakdown

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

Requests Now

34

After Optimization

18

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

Accessibility Review

trip.ee accessibility score

95

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

Links do not have a discernible name

Best Practices

trip.ee 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

High

Page has valid source maps

SEO Factors

trip.ee SEO score

98

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ET

  • Language Claimed

    ET

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trip.ee can be misinterpreted by Google and other search engines. Our service has detected that Estonian is used on the page, and it matches the claimed language. Our system also found out that Trip.ee 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 Trip. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: