Tools & Wizards About Us
gentility.co screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

gentility.co

gentility.co

Page Load Speed

7.4 sec in total

First Response

278 ms

Resources Loaded

3.2 sec

Page Rendered

3.9 sec

gentility.co screenshot

About Website

Welcome to gentility.co homepage info - get ready to check Gentility best content right away, or after learning these important things about gentility.co

This domain may be for sale!

Visit gentility.co

Key Findings

We analyzed Gentility.co page load time and found that the first response time was 278 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

gentility.co performance score

0

Network Requests Diagram

gentility.co

278 ms

css

66 ms

base.css

167 ms

skeleton.css

151 ms

supersized.css

163 ms

Our browser made a total of 162 requests to load all elements on the main page. We found that 75% of them (121 requests) were addressed to the original Gentility.co, 16% (26 requests) were made to Maps.googleapis.com and 5% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (804 ms) belongs to the original domain Gentility.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (25%)

Content Size

4.6 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gentility.co main page is 4.6 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. 65% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 170.3 kB

  • Original 200.4 kB
  • After minification 143.6 kB
  • After compression 30.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 56.8 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 170.3 kB or 85% of the original size.

Image Optimization

-8%

Potential reduce by 267.4 kB

  • Original 3.5 MB
  • After minification 3.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. Gentility images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 580.0 kB

  • Original 828.7 kB
  • After minification 762.9 kB
  • After compression 248.7 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 580.0 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 111.9 kB

  • Original 129.3 kB
  • After minification 84.6 kB
  • After compression 17.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. Gentility.co needs all CSS files to be minified and compressed as it can save up to 111.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (39%)

Requests Now

161

After Optimization

98

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gentility.co

gentility.co

278 ms

css

css

66 ms

base.css

base.css

167 ms

skeleton.css

skeleton.css

151 ms

supersized.css

supersized.css

163 ms

supersized.shutter.css

supersized.shutter.css

156 ms

settings.css

settings.css

228 ms

jackbox_hovers.css

jackbox_hovers.css

195 ms

jackbox.css

jackbox.css

246 ms

zoomshowcase.css

zoomshowcase.css

277 ms

screen.css

screen.css

248 ms

jquery.min.js

jquery.min.js

65 ms

jquery-ui.min.js

jquery-ui.min.js

85 ms

webfont.js

webfont.js

84 ms

jquery.parallax-1.1.3.js

jquery.parallax-1.1.3.js

267 ms

jquery.localscroll-1.2.7-min.js

jquery.localscroll-1.2.7-min.js

325 ms

jquery.scrollTo-1.4.3.js

jquery.scrollTo-1.4.3.js

326 ms

jacked.min.js

jacked.min.js

328 ms

slackBlur.min.js

slackBlur.min.js

329 ms

jquery.easing.min.js

jquery.easing.min.js

344 ms

supersized.3.2.7.js

supersized.3.2.7.js

353 ms

supersized.shutter.js

supersized.shutter.js

371 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

395 ms

jquery.tipsy.js

jquery.tipsy.js

410 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

384 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

448 ms

jquery.themepunch.megafoliopro.js

jquery.themepunch.megafoliopro.js

440 ms

js

js

110 ms

jquery.address-1.5.min.js

jquery.address-1.5.min.js

485 ms

jackbox-swipe.js

jackbox-swipe.js

468 ms

jackbox.js

jackbox.js

492 ms

jquick.min.js

jquick.min.js

495 ms

jquick.zoomshowcase.js

jquick.zoomshowcase.js

524 ms

jquery.carouFredSel-6.2.0-packed.js

jquery.carouFredSel-6.2.0-packed.js

548 ms

kenway.js

kenway.js

533 ms

analytics.js

analytics.js

19 ms

collect

collect

16 ms

grid1.png

grid1.png

126 ms

logo.png

logo.png

123 ms

linkedin.png

linkedin.png

230 ms

facebook.png

facebook.png

201 ms

twitter.png

twitter.png

232 ms

instagram.png

instagram.png

132 ms

pinterest.png

pinterest.png

239 ms

google_plus.png

google_plus.png

259 ms

back.png

back.png

218 ms

forward.png

forward.png

264 ms

About_02B.jpg

About_02B.jpg

376 ms

blank.jpg

blank.jpg

328 ms

3_1.jpg

3_1.jpg

431 ms

3_2.jpg

3_2.jpg

408 ms

3_44.jpg

3_44.jpg

406 ms

3_3.jpg

3_3.jpg

389 ms

3_4.jpg

3_4.jpg

485 ms

3_5.jpg

3_5.jpg

579 ms

3_6.jpg

3_6.jpg

516 ms

3_7.jpg

3_7.jpg

488 ms

3_8.jpg

3_8.jpg

500 ms

3_9.jpg

3_9.jpg

589 ms

3_10.jpg

3_10.jpg

647 ms

3_11.jpg

3_11.jpg

564 ms

3_50.jpg

3_50.jpg

637 ms

3_51.jpg

3_51.jpg

647 ms

3_52.jpg

3_52.jpg

646 ms

3_53.jpg

3_53.jpg

724 ms

3_54.jpg

3_54.jpg

742 ms

3_55.jpg

3_55.jpg

784 ms

time.jpg

time.jpg

744 ms

value.jpg

value.jpg

731 ms

access.jpg

access.jpg

741 ms

influence.jpg

influence.jpg

804 ms

distinction.jpg

distinction.jpg

800 ms

secrecy.jpg

secrecy.jpg

717 ms

2__.png

2__.png

727 ms

1__.png

1__.png

720 ms

3__.png

3__.png

732 ms

1.jpg

1.jpg

685 ms

2.jpg

2.jpg

664 ms

3.jpg

3.jpg

690 ms

4.jpg

4.jpg

698 ms

5.jpg

5.jpg

685 ms

6.jpg

6.jpg

679 ms

7.jpg

7.jpg

690 ms

8.jpg

8.jpg

629 ms

Legrandmag.png

Legrandmag.png

633 ms

LouLaVie.png

LouLaVie.png

616 ms

76Cal_logo.png

76Cal_logo.png

603 ms

Maloman.png

Maloman.png

605 ms

15.png

15.png

601 ms

06.png

06.png

550 ms

10.png

10.png

588 ms

11.png

11.png

585 ms

04.png

04.png

575 ms

03.png

03.png

519 ms

12.png

12.png

509 ms

17.png

17.png

516 ms

16.png

16.png

512 ms

05.png

05.png

506 ms

01.png

01.png

520 ms

07.png

07.png

502 ms

08.png

08.png

446 ms

13.png

13.png

445 ms

14.png

14.png

473 ms

01.jpg

01.jpg

475 ms

02.jpg

02.jpg

482 ms

03.jpg

03.jpg

470 ms

04.jpg

04.jpg

452 ms

image.php

image.php

588 ms

linkedin.png

linkedin.png

469 ms

facebook.png

facebook.png

448 ms

twitter.png

twitter.png

463 ms

about.jpg

about.jpg

566 ms

acc.png

acc.png

460 ms

bullet.png

bullet.png

472 ms

philosophy.jpg

philosophy.jpg

791 ms

quote.png

quote.png

456 ms

services.jpg

services.jpg

648 ms

grain.png

grain.png

490 ms

plus.png

plus.png

498 ms

magnify.png

magnify.png

518 ms

interests.jpg

interests.jpg

595 ms

web.png

web.png

503 ms

memberships.jpg

memberships.jpg

642 ms

insider.jpg

insider.jpg

674 ms

instagram.png

instagram.png

560 ms

pinterest.png

pinterest.png

650 ms

google_plus.png

google_plus.png

617 ms

common.js

common.js

22 ms

map.js

map.js

55 ms

util.js

util.js

102 ms

marker.js

marker.js

101 ms

onion.js

onion.js

29 ms

openhand_8_8.cur

openhand_8_8.cur

121 ms

stats.js

stats.js

38 ms

controls.js

controls.js

40 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

132 ms

css

css

61 ms

transparent.png

transparent.png

28 ms

map_icon_black.png

map_icon_black.png

95 ms

google4.png

google4.png

14 ms

mapcnt6.png

mapcnt6.png

41 ms

sv5.png

sv5.png

40 ms

tmapctrl.png

tmapctrl.png

42 ms

tmapctrl4.png

tmapctrl4.png

43 ms

google_white5.png

google_white5.png

42 ms

vt

vt

67 ms

vt

vt

89 ms

vt

vt

65 ms

vt

vt

70 ms

vt

vt

78 ms

vt

vt

102 ms

vt

vt

109 ms

vt

vt

89 ms

vt

vt

103 ms

vt

vt

141 ms

vt

vt

131 ms

vt

vt

133 ms

vt

vt

163 ms

vt

vt

141 ms

vt

vt

142 ms

vt

vt

216 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

41 ms

SEO Factors

gentility.co SEO score

0

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 Gentility.co 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 Gentility.co 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

gentility.co

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