Tools & Wizards About Us
future.travel screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

future.travel

Future.Travel - Best travel website for airline tickets - No Booking Fee

Page Load Speed

2.1 sec in total

First Response

149 ms

Resources Loaded

1.8 sec

Page Rendered

171 ms

future.travel screenshot

About Website

Visit future.travel now to see the best up-to-date Future content and also check out these interesting facts you probably never knew about future.travel

Future.Travel finds discounted flights via a unique flight search & compare method. The best travel site for cheap business class tickets with no booking fee.

Visit future.travel

Key Findings

We analyzed Future.travel page load time and found that the first response time was 149 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

future.travel performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.563

12/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

future.travel

149 ms

future.travel

482 ms

gtm.js

56 ms

futuretravel_logo.jpg

186 ms

sprite2.png

327 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 75% of them (33 requests) were addressed to the original Future.travel, 7% (3 requests) were made to Image.providesupport.com and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (570 ms) belongs to the original domain Future.travel.

Page Optimization Overview & Recommendations

Page size can be reduced by 58.5 kB (12%)

Content Size

499.7 kB

After Optimization

441.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Future.travel main page is 499.7 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. Images take 186.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 48.6 kB

  • Original 63.6 kB
  • After minification 63.1 kB
  • After compression 15.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. 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 48.6 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 5.2 kB

  • Original 186.8 kB
  • After minification 181.5 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. Future images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 230 B

  • Original 176.2 kB
  • After minification 176.2 kB
  • After compression 176.0 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

-6%

Potential reduce by 4.4 kB

  • Original 73.1 kB
  • After minification 72.2 kB
  • After compression 68.7 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. Future.travel has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (68%)

Requests Now

37

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

future.travel

future.travel

149 ms

future.travel

future.travel

482 ms

gtm.js

gtm.js

56 ms

futuretravel_logo.jpg

futuretravel_logo.jpg

186 ms

sprite2.png

sprite2.png

327 ms

bg-home.jpg

bg-home.jpg

501 ms

icon_buy.png

icon_buy.png

330 ms

icon_target.png

icon_target.png

329 ms

icon_star.png

icon_star.png

329 ms

arrow.png

arrow.png

328 ms

lozad.min.js

lozad.min.js

327 ms

all-2.js

all-2.js

570 ms

owl.carousel.min.js

owl.carousel.min.js

329 ms

jquery.validationEngine.js

jquery.validationEngine.js

327 ms

jquery.validationEngine-en.js

jquery.validationEngine-en.js

328 ms

sprite-1.png

sprite-1.png

474 ms

safe-textlink.js

safe-textlink.js

106 ms

analytics.js

analytics.js

36 ms

insight.min.js

insight.min.js

119 ms

fbevents.js

fbevents.js

30 ms

static.js

static.js

67 ms

collect

collect

21 ms

0d7zta0l2jav00zb5uu9qqlxc5

0d7zta0l2jav00zb5uu9qqlxc5

43 ms

collect

collect

129 ms

js

js

33 ms

ga-audiences

ga-audiences

39 ms

all.css

all.css

134 ms

font-awesome.min.css

font-awesome.min.css

62 ms

v6-fontawesome.min.css

v6-fontawesome.min.css

129 ms

v6-brands.min.css

v6-brands.min.css

65 ms

v4-font-face.min.css

v4-font-face.min.css

65 ms

new-style.css

new-style.css

67 ms

owl.carousel.min.css

owl.carousel.min.css

121 ms

owl.theme.default.min.css

owl.theme.default.min.css

128 ms

zalo.ico

zalo.ico

68 ms

icon-imessage.png

icon-imessage.png

61 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

61 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

255 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

66 ms

fa-regular-400.ttf

fa-regular-400.ttf

131 ms

fa-brands-400.ttf

fa-brands-400.ttf

139 ms

fa-solid-900.ttf

fa-solid-900.ttf

264 ms

icon-calendar.png

icon-calendar.png

115 ms

AjaxLoader.gif

AjaxLoader.gif

62 ms

Accessibility Review

future.travel accessibility score

90

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

Form elements do not have associated labels

Best Practices

future.travel 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

future.travel SEO score

89

Search Engine Optimization Advices

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 Future.travel 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 Future.travel 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

future.travel

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