Tools & Wizards About Us
eastwego.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

eastwego.com

East We Go |Travel blog | Round the world backpacking trip

Page Load Speed

3.6 sec in total

First Response

973 ms

Resources Loaded

2.4 sec

Page Rendered

291 ms

eastwego.com screenshot

About Website

Welcome to eastwego.com homepage info - get ready to check East We Go best content right away, or after learning these important things about eastwego.com

East We Go |Travel blog of a Polish-Portuguese couple traveling around the world. Backpacking through Europe, Asia and South America without almost any plan and commitments.

Visit eastwego.com

Key Findings

We analyzed Eastwego.com page load time and found that the first response time was 973 ms and then it took 2.6 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

eastwego.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value1,950 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

eastwego.com

973 ms

wp-emoji-release.min.js

200 ms

font-awesome.min.css

213 ms

sbi-styles.min.css

210 ms

style.min.css

211 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 67% of them (48 requests) were addressed to the original Eastwego.com, 14% (10 requests) were made to Static.xx.fbcdn.net and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (973 ms) belongs to the original domain Eastwego.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 92.2 kB (6%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eastwego.com main page is 1.4 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. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 82.0 kB

  • Original 99.6 kB
  • After minification 95.8 kB
  • After compression 17.6 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 82.0 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 2.5 kB

  • Original 1.2 MB
  • After minification 1.2 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. East We Go images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.9 kB

  • Original 129.4 kB
  • After minification 129.4 kB
  • After compression 126.5 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

-8%

Potential reduce by 4.7 kB

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

Requests Breakdown

Number of requests can be reduced by 30 (45%)

Requests Now

67

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eastwego.com

eastwego.com

973 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

200 ms

font-awesome.min.css

font-awesome.min.css

213 ms

sbi-styles.min.css

sbi-styles.min.css

210 ms

style.min.css

style.min.css

211 ms

style.css

style.css

327 ms

css

css

22 ms

css

css

41 ms

bos_searchbox.css

bos_searchbox.css

216 ms

jetpack.css

jetpack.css

312 ms

jquery.min.js

jquery.min.js

417 ms

jquery-migrate.min.js

jquery-migrate.min.js

316 ms

socialFeed.js

socialFeed.js

522 ms

tie-scripts.js

tie-scripts.js

348 ms

facebook-embed.min.js

facebook-embed.min.js

342 ms

bos_main.js

bos_main.js

342 ms

bos_date.js

bos_date.js

350 ms

wp-embed.min.js

wp-embed.min.js

436 ms

jetpack-carousel.min.js

jetpack-carousel.min.js

437 ms

e-202436.js

e-202436.js

14 ms

analytics.js

analytics.js

25 ms

Backgroung-pic-small2.jpg

Backgroung-pic-small2.jpg

596 ms

header-with-lobster-logo-small-good.jpg

header-with-lobster-logo-small-good.jpg

433 ms

DSCF2279-620x330.jpg

DSCF2279-620x330.jpg

325 ms

DSCF7136-620x330.jpg

DSCF7136-620x330.jpg

419 ms

DSCF7086-620x330.jpg

DSCF7086-620x330.jpg

110 ms

Inle-Lake-69-620x330.jpg

Inle-Lake-69-620x330.jpg

313 ms

G0072995-620x330.jpg

G0072995-620x330.jpg

317 ms

DSCF2279-300x160.jpg

DSCF2279-300x160.jpg

419 ms

DSCF7136-300x160.jpg

DSCF7136-300x160.jpg

420 ms

DSCF7086-300x160.jpg

DSCF7086-300x160.jpg

433 ms

Inle-Lake-69-300x160.jpg

Inle-Lake-69-300x160.jpg

524 ms

G0072995-300x160.jpg

G0072995-300x160.jpg

627 ms

Inle-Lake-51-300x160.jpg

Inle-Lake-51-300x160.jpg

524 ms

Cameron-Highlands-32-300x160.jpg

Cameron-Highlands-32-300x160.jpg

599 ms

Bandung-16-300x160.jpg

Bandung-16-300x160.jpg

544 ms

Ijen-Crater-12-300x160.jpg

Ijen-Crater-12-300x160.jpg

626 ms

Mawlamyine-60-300x160.jpg

Mawlamyine-60-300x160.jpg

628 ms

DSCF6565-800x559-300x210.jpg

DSCF6565-800x559-300x210.jpg

652 ms

DSCF2279-70x70.jpg

DSCF2279-70x70.jpg

708 ms

DSCF7136-70x70.jpg

DSCF7136-70x70.jpg

707 ms

DSCF7086-70x70.jpg

DSCF7086-70x70.jpg

731 ms

Inle-Lake-69-70x70.jpg

Inle-Lake-69-70x70.jpg

732 ms

G0072995-70x70.jpg

G0072995-70x70.jpg

732 ms

Cameron-Highlands-32-70x70.jpg

Cameron-Highlands-32-70x70.jpg

759 ms

Ijen-Crater-12-70x70.jpg

Ijen-Crater-12-70x70.jpg

816 ms

Mawlamyine-60-70x70.jpg

Mawlamyine-60-70x70.jpg

821 ms

top-shadow.png

top-shadow.png

815 ms

black-loader.gif

black-loader.gif

816 ms

tiefontello.svg

tiefontello.svg

817 ms

tiefontello.woff

tiefontello.woff

847 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUE.ttf

26 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZogUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZogUE.ttf

26 ms

collect

collect

62 ms

sidebar-bullet.png

sidebar-bullet.png

879 ms

neILzCirqoswsqX9_oU.ttf

neILzCirqoswsqX9_oU.ttf

94 ms

likebox.php

likebox.php

112 ms

sdk.js

sdk.js

19 ms

js

js

63 ms

sdk.js

sdk.js

5 ms

lFC1eVji7gN.css

lFC1eVji7gN.css

16 ms

fTDJAhN6I0H.js

fTDJAhN6I0H.js

21 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

47 ms

pLoSlJD7y1F.js

pLoSlJD7y1F.js

49 ms

Mw5y7Z3v-mj.js

Mw5y7Z3v-mj.js

48 ms

Glud--w-qOK.js

Glud--w-qOK.js

46 ms

IUvgVkA30DJ.js

IUvgVkA30DJ.js

46 ms

p55HfXW__mM.js

p55HfXW__mM.js

47 ms

308852647_529733112487282_8476898733310124747_n.jpg

308852647_529733112487282_8476898733310124747_n.jpg

230 ms

Dpom1HQzAgH.js

Dpom1HQzAgH.js

16 ms

309398141_529733115820615_7957249110994687360_n.jpg

309398141_529733115820615_7957249110994687360_n.jpg

90 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

15 ms

Accessibility Review

eastwego.com accessibility score

55

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Heading elements are not in a sequentially-descending order

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

eastwego.com best practices score

83

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

SEO Factors

eastwego.com 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 Eastwego.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 Eastwego.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

eastwego.com

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