Tools & Wizards About Us
geenee.com screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    88% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

geenee.com

Geenee Holiday Home Exchange

Page Load Speed

1.7 sec in total

First Response

231 ms

Resources Loaded

1.4 sec

Page Rendered

109 ms

geenee.com screenshot

About Website

Visit geenee.com now to see the best up-to-date Geenee content and also check out these interesting facts you probably never knew about geenee.com

Home exchange holidays puts you at the heart of the world´s coolest cities. Geenee makes home swapping simple and secure. Find your perfect holiday home

Visit geenee.com

Key Findings

We analyzed Geenee.com page load time and found that the first response time was 231 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

geenee.com performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

geenee.com

231 ms

indexmain.php

483 ms

basic.css

138 ms

lang_en.css

196 ms

landing.css

199 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 93% of them (27 requests) were addressed to the original Geenee.com, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (483 ms) belongs to the original domain Geenee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 93.4 kB (55%)

Content Size

171.3 kB

After Optimization

77.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-0%

Potential reduce by 0 B

  • Original 583 B

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. This web page is already compressed.

Image Optimization

-7%

Potential reduce by 2.5 kB

  • Original 33.2 kB
  • After minification 30.7 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. Geenee images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 79.9 kB

  • Original 123.9 kB
  • After minification 116.7 kB
  • After compression 44.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 79.9 kB or 64% of the original size.

CSS Optimization

-81%

Potential reduce by 11.1 kB

  • Original 13.6 kB
  • After minification 8.2 kB
  • After compression 2.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. Geenee.com needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (37%)

Requests Now

27

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

geenee.com

geenee.com

231 ms

indexmain.php

indexmain.php

483 ms

basic.css

basic.css

138 ms

lang_en.css

lang_en.css

196 ms

landing.css

landing.css

199 ms

sitewide.js

sitewide.js

320 ms

jquery.js

jquery.js

482 ms

urchin.js

urchin.js

6 ms

landing-geenee.gif

landing-geenee.gif

81 ms

landing-quote.gif

landing-quote.gif

77 ms

1050l.jpeg

1050l.jpeg

80 ms

1071l.jpeg

1071l.jpeg

80 ms

1033l.jpeg

1033l.jpeg

137 ms

1097l.jpeg

1097l.jpeg

148 ms

1108l.jpeg

1108l.jpeg

214 ms

1112l.jpeg

1112l.jpeg

153 ms

go-landing.gif

go-landing.gif

149 ms

landing-top.gif

landing-top.gif

77 ms

landing-join1.gif

landing-join1.gif

74 ms

landing-joinBody.gif

landing-joinBody.gif

77 ms

landing-arrow.gif

landing-arrow.gif

76 ms

landing-checkout.gif

landing-checkout.gif

75 ms

dark-arrow.gif

dark-arrow.gif

105 ms

landing-coolest.gif

landing-coolest.gif

148 ms

landing-simple-and-secure.gif

landing-simple-and-secure.gif

146 ms

light-arrow.gif

light-arrow.gif

146 ms

bar.gif

bar.gif

144 ms

__utm.gif

__utm.gif

6 ms

print.css

print.css

74 ms

Accessibility Review

geenee.com accessibility score

93

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.

Best Practices

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

High

Page has valid source maps

SEO Factors

geenee.com SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geenee.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Geenee.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

geenee.com

Open Graph description is not detected on the main page of Geenee. 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: