Tools & Wizards About Us
wouldbetraveller.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

wouldbetraveller.com

Would Be Traveller | The Ethical Travel & Adventure Blog

Page Load Speed

2.9 sec in total

First Response

455 ms

Resources Loaded

2.1 sec

Page Rendered

303 ms

wouldbetraveller.com screenshot

About Website

Click here to check amazing Would Be Traveller content. Otherwise, check out these important facts you probably never knew about wouldbetraveller.com

Discover how to travel more ethically with our guides to the most sustainable destinations, travel products and accommodation across the world.

Visit wouldbetraveller.com

Key Findings

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

Performance Metrics

wouldbetraveller.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.452

20/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

Network Requests Diagram

www.wouldbetraveller.com

455 ms

96cae.css

25 ms

818c0.js

70 ms

js

166 ms

86e9b.js

349 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 79% of them (19 requests) were addressed to the original Wouldbetraveller.com, 8% (2 requests) were made to Googletagmanager.com and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (489 ms) belongs to the original domain Wouldbetraveller.com.

Page Optimization Overview & Recommendations

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

Content Size

386.7 kB

After Optimization

306.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wouldbetraveller.com main page is 386.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. 50% of websites need less resources to load. Javascripts take 155.2 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 62.3 kB

  • Original 75.0 kB
  • After minification 75.0 kB
  • After compression 12.7 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 62.3 kB or 83% of the original size.

Image Optimization

-24%

Potential reduce by 17.9 kB

  • Original 74.0 kB
  • After minification 56.1 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. Obviously, Would Be Traveller needs image optimization as it can save up to 17.9 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 78 B

  • Original 155.2 kB
  • After minification 155.2 kB
  • After compression 155.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 7 (32%)

Requests Now

22

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wouldbetraveller.com

www.wouldbetraveller.com

455 ms

96cae.css

96cae.css

25 ms

818c0.js

818c0.js

70 ms

js

js

166 ms

86e9b.js

86e9b.js

349 ms

f37b2.js

f37b2.js

154 ms

fedf1.js

fedf1.js

155 ms

e72d4.js

e72d4.js

489 ms

js

js

101 ms

analytics.js

analytics.js

21 ms

collect

collect

53 ms

fl-icons.ttf

fl-icons.ttf

326 ms

collect

collect

62 ms

WBT-Grey-and-Colour-e1620322792683.png

WBT-Grey-and-Colour-e1620322792683.png

17 ms

would-be-traveller-jungle-lodges-costa-rica-180x180.jpg

would-be-traveller-jungle-lodges-costa-rica-180x180.jpg

399 ms

would-be-traveller-hotels-with-a-view-of-the-pyramids-180x180.jpg

would-be-traveller-hotels-with-a-view-of-the-pyramids-180x180.jpg

27 ms

would-be-traveller-desert-clothes-180x180.jpg

would-be-traveller-desert-clothes-180x180.jpg

15 ms

would-be-traveller-egypt-packing-list-180x180.jpg

would-be-traveller-egypt-packing-list-180x180.jpg

34 ms

would-be-traveller-hotels-with-a-view-of-the-pyramids-180x180.jpg

would-be-traveller-hotels-with-a-view-of-the-pyramids-180x180.jpg

73 ms

would-be-traveller-desert-clothes-180x180.jpg

would-be-traveller-desert-clothes-180x180.jpg

74 ms

would-be-traveller-egypt-packing-list-180x180.jpg

would-be-traveller-egypt-packing-list-180x180.jpg

306 ms

would-be-traveller-hotels-with-a-view-of-the-pyramids-180x180.jpg

would-be-traveller-hotels-with-a-view-of-the-pyramids-180x180.jpg

303 ms

would-be-traveller-desert-clothes-180x180.jpg

would-be-traveller-desert-clothes-180x180.jpg

30 ms

Would-Be-Traveller-10-days-in-Costa-Rica-itinerary-1440x500.jpg

Would-Be-Traveller-10-days-in-Costa-Rica-itinerary-1440x500.jpg

14 ms

Accessibility Review

wouldbetraveller.com accessibility score

83

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-hidden="true"] elements contain focusable descendents

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

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

wouldbetraveller.com 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

wouldbetraveller.com SEO score

99

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

wouldbetraveller.com

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