Tools & Wizards About Us
travelog.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

travelog.com

Travelog - Book Activities, Tours and Holiday Packages

Page Load Speed

7.1 sec in total

First Response

475 ms

Resources Loaded

6.6 sec

Page Rendered

85 ms

travelog.com screenshot

About Website

Welcome to travelog.com homepage info - get ready to check Travelog best content for Malaysia right away, or after learning these important things about travelog.com

Book and Sell sightseeing tours, attractions, excursions, things to do, fun activities and holiday package from around the world. Save money and book directly from local suppliers.

Visit travelog.com

Key Findings

We analyzed Travelog.com page load time and found that the first response time was 475 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

travelog.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,620 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

travelog.com

475 ms

travelog.com

4618 ms

gtm.js

91 ms

fbevents.js

40 ms

events.js

69 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 29% of them (4 requests) were addressed to the original Travelog.com, 29% (4 requests) were made to Pro.fontawesome.com and 14% (2 requests) were made to Analytics.tiktok.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Travelog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 201.5 kB (49%)

Content Size

409.9 kB

After Optimization

208.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Travelog.com main page is 409.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. HTML takes 235.7 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 200.8 kB

  • Original 235.7 kB
  • After minification 195.9 kB
  • After compression 35.0 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. This page needs HTML code to be minified as it can gain 39.9 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 200.8 kB or 85% of the original size.

JavaScript Optimization

-0%

Potential reduce by 10 B

  • Original 116.9 kB
  • After minification 116.9 kB
  • After compression 116.9 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.

CSS Optimization

-1%

Potential reduce by 742 B

  • Original 57.2 kB
  • After minification 57.2 kB
  • After compression 56.4 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. Travelog.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (67%)

Requests Now

9

After Optimization

3

  • JavaScript
  • CSS

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

Network Requests Diagram

travelog.com

travelog.com

475 ms

travelog.com

travelog.com

4618 ms

gtm.js

gtm.js

91 ms

fbevents.js

fbevents.js

40 ms

events.js

events.js

69 ms

events.js

events.js

68 ms

shopifyWidget.js

shopifyWidget.js

122 ms

all.css

all.css

67 ms

consumer.css

consumer.css

250 ms

js

js

109 ms

consumer.js

consumer.js

1443 ms

fa-solid-900.woff

fa-solid-900.woff

23 ms

fa-regular-400.woff

fa-regular-400.woff

32 ms

fa-light-300.woff

fa-light-300.woff

32 ms

Accessibility Review

travelog.com accessibility score

59

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

travelog.com best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

travelog.com SEO score

83

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

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

travelog.com

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