Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

interactive.travelweekly.com

Travel Weekly | Voice of the Travel Industry, Hotels & Destinations: Travel Weekly

Page Load Speed

5.1 sec in total

First Response

82 ms

Resources Loaded

3.4 sec

Page Rendered

1.7 sec

About Website

Welcome to interactive.travelweekly.com homepage info - get ready to check Interactive Travel Weekly best content for United States right away, or after learning these important things about interactive.travelweekly.com

The travel industry's trusted source for breaking U.S. and international news, destination information, hotel headlines, cruise itineraries, travel trends, expert insight and beyond.

Visit interactive.travelweekly.com

Key Findings

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

Performance Metrics

interactive.travelweekly.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value21.1 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value10,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.312

37/100

15%

TTI (Time to Interactive)

Value37.0 s

0/100

10%

Network Requests Diagram

interactive.travelweekly.com

82 ms

www.travelweekly.com

41 ms

www.travelweekly.com

404 ms

style.css

35 ms

scripts.min.js

52 ms

Our browser made a total of 299 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Interactive.travelweekly.com, 66% (198 requests) were made to Ik.imgkit.net and 6% (19 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (986 ms) relates to the external source Syndication.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (17%)

Content Size

6.3 MB

After Optimization

5.2 MB

In fact, the total size of Interactive.travelweekly.com main page is 6.3 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. Only a small number of websites need less resources to load. Images take 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 405.7 kB

  • Original 476.2 kB
  • After minification 469.3 kB
  • After compression 70.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 405.7 kB or 85% of the original size.

Image Optimization

-7%

Potential reduce by 352.1 kB

  • Original 4.9 MB
  • After minification 4.6 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. Interactive Travel Weekly images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 342.8 kB

  • Original 848.0 kB
  • After minification 848.0 kB
  • After compression 505.2 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 342.8 kB or 40% of the original size.

CSS Optimization

-0%

Potential reduce by 140 B

  • Original 61.1 kB
  • After minification 61.1 kB
  • After compression 61.0 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. Interactive.travelweekly.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

285

After Optimization

233

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

Accessibility Review

interactive.travelweekly.com accessibility score

84

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-*] attributes do not have valid values

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

Best Practices

interactive.travelweekly.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

interactive.travelweekly.com SEO score

76

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Interactive.travelweekly.com 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 Interactive.travelweekly.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

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