Tools & Wizards About Us
where2go2.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

where2go2.com

Where2go2.Com Vacation Rentals - Holiday Rental Villas, Condos, Beach Houses

Page Load Speed

1.6 sec in total

First Response

98 ms

Resources Loaded

1.3 sec

Page Rendered

177 ms

where2go2.com screenshot

About Website

Welcome to where2go2.com homepage info - get ready to check Where2go2 best content right away, or after learning these important things about where2go2.com

Vacation Rentals - International vacation rental properties including beach houses, villas, condos, and cottages

Visit where2go2.com

Key Findings

We analyzed Where2go2.com page load time and found that the first response time was 98 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

where2go2.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value5.4 s

57/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.377

28/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

where2go2.com

98 ms

www.where2go2.com

155 ms

css

38 ms

bootstrap.css

334 ms

bootstrap-responsive.css

197 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 83% of them (38 requests) were addressed to the original Where2go2.com, 11% (5 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (611 ms) belongs to the original domain Where2go2.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 643.0 kB (57%)

Content Size

1.1 MB

After Optimization

475.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Where2go2.com main page is 1.1 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. 45% of websites need less resources to load. CSS take 424.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 12.0 kB

  • Original 15.1 kB
  • After minification 10.9 kB
  • After compression 3.1 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 4.2 kB, which is 28% 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 12.0 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 9.0 kB

  • Original 349.3 kB
  • After minification 340.2 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. Where2go2 images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 250.9 kB

  • Original 330.1 kB
  • After minification 252.3 kB
  • After compression 79.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 250.9 kB or 76% of the original size.

CSS Optimization

-87%

Potential reduce by 371.0 kB

  • Original 424.1 kB
  • After minification 328.5 kB
  • After compression 53.1 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. Where2go2.com needs all CSS files to be minified and compressed as it can save up to 371.0 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (76%)

Requests Now

38

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

where2go2.com

where2go2.com

98 ms

www.where2go2.com

www.where2go2.com

155 ms

css

css

38 ms

bootstrap.css

bootstrap.css

334 ms

bootstrap-responsive.css

bootstrap-responsive.css

197 ms

flexslider.css

flexslider.css

172 ms

prettyPhoto.css

prettyPhoto.css

198 ms

camera.css

camera.css

257 ms

jquery.bxslider.css

jquery.bxslider.css

230 ms

cslider.css

cslider.css

237 ms

style.css

style.css

356 ms

default.css

default.css

327 ms

jquery.js

jquery.js

446 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

330 ms

bootstrap.js

bootstrap.js

455 ms

modernizr.custom.js

modernizr.custom.js

399 ms

toucheffects.js

toucheffects.js

390 ms

prettify.js

prettify.js

405 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

434 ms

jquery.cslider.js

jquery.cslider.js

433 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

513 ms

jquery.quicksand.js

jquery.quicksand.js

513 ms

setting.js

setting.js

511 ms

jquery.flexslider.js

jquery.flexslider.js

611 ms

animate.js

animate.js

568 ms

inview.js

inview.js

567 ms

custom.js

custom.js

566 ms

header_left_main.jpg

header_left_main.jpg

599 ms

prettify.css

prettify.css

222 ms

font-awesome.css

font-awesome.css

339 ms

overwrite.css

overwrite.css

341 ms

animate.css

animate.css

345 ms

shortcodes.css

shortcodes.css

331 ms

flexiproduct.js

flexiproduct.js

107 ms

bg.jpg

bg.jpg

101 ms

479vr_a.jpg

479vr_a.jpg

92 ms

923vr_a.jpg

923vr_a.jpg

92 ms

139vr_a.jpg

139vr_a.jpg

92 ms

706vr_a.jpg

706vr_a.jpg

92 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

24 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

32 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

38 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

49 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

49 ms

flexiproduct.html

flexiproduct.html

243 ms

Accessibility Review

where2go2.com accessibility score

71

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

<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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

where2go2.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

where2go2.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 Where2go2.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 Where2go2.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

where2go2.com

Open Graph description is not detected on the main page of Where2go2. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: