Tools & Wizards About Us
207pearl.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

207pearl.com

207 Pearl Lane, Menlo Park - Presented by: Katy Worthing - www.207Pearl.com

Page Load Speed

3.4 sec in total

First Response

103 ms

Resources Loaded

2.6 sec

Page Rendered

734 ms

207pearl.com screenshot

About Website

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

207 Pearl Ln Menlo Park, CA 94025, Exceptional Menlo Park Home, Presented by Katy Worthing - Sotheby's International Realty www.207Pearl.com

Visit 207pearl.com

Key Findings

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

Performance Metrics

207pearl.com performance score

0

Network Requests Diagram

207pearl.com

103 ms

www.207pearl.com

811 ms

settings.css

74 ms

blueimp-gallery.min.css

102 ms

integrity-light.css

161 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 207pearl.com, 17% (21 requests) were made to B90d3bd209cbe0031bcd-b6b1e8877217d1eb31891b02371f5323.r11.cf1.rackcdn.com and 16% (20 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source 962dd788c734bcab04a1-883cc502eff526e75f83e5df061a3d2d.r29.cf1.rackcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (40%)

Content Size

5.1 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 207pearl.com main page is 5.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 47.2 kB

  • Original 59.6 kB
  • After minification 53.1 kB
  • After compression 12.3 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 6.5 kB, which is 11% 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 47.2 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 145.2 kB

  • Original 2.4 MB
  • After minification 2.3 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. 207 Pearl images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 1.6 MB

  • Original 2.3 MB
  • After minification 2.3 MB
  • After compression 712.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 1.6 MB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 252.1 kB

  • Original 298.8 kB
  • After minification 270.8 kB
  • After compression 46.7 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. 207pearl.com needs all CSS files to be minified and compressed as it can save up to 252.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 78 (74%)

Requests Now

106

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

207pearl.com

207pearl.com

103 ms

www.207pearl.com

www.207pearl.com

811 ms

settings.css

settings.css

74 ms

blueimp-gallery.min.css

blueimp-gallery.min.css

102 ms

integrity-light.css

integrity-light.css

161 ms

style-mod.css

style-mod.css

133 ms

css

css

26 ms

fa-icon-classes.css

fa-icon-classes.css

137 ms

jquery.js

jquery.js

240 ms

jquery-migrate.min.js

jquery-migrate.min.js

139 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

181 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

186 ms

x-head-mod.min.js

x-head-mod.min.js

180 ms

cs-head.min.js

cs-head.min.js

179 ms

javascript.gp

javascript.gp

187 ms

show-walkscore-tile.php

show-walkscore-tile.php

12 ms

x-custom.js

x-custom.js

151 ms

x-body-mod.min.js

x-body-mod.min.js

160 ms

comment-reply.min.js

comment-reply.min.js

172 ms

cs-body.min.js

cs-body.min.js

162 ms

blueimp-gallery.min.js

blueimp-gallery.min.js

180 ms

buttons.js

buttons.js

9 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

75 ms

featherlight.min.css

featherlight.min.css

5 ms

featherlight.min.js

featherlight.min.js

6 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

250 ms

01.jpg

01.jpg

604 ms

Sothebys_2014_REV.png

Sothebys_2014_REV.png

57 ms

x-bg-grid-noise.png

x-bg-grid-noise.png

54 ms

01_800px.jpg

01_800px.jpg

595 ms

CC2_800px.jpg

CC2_800px.jpg

597 ms

09.jpg

09.jpg

1259 ms

Katy01_Crop_2.2015__thumbnail.jpg

Katy01_Crop_2.2015__thumbnail.jpg

599 ms

houzz-icon1.png

houzz-icon1.png

52 ms

BTu4SsVveqk58cdYjlaM9g.ttf

BTu4SsVveqk58cdYjlaM9g.ttf

51 ms

vDvcuXwZxUMLuTfuLrSLpA.ttf

vDvcuXwZxUMLuTfuLrSLpA.ttf

78 ms

4GwpJM7qx9X5Obd9KsnKxQ.ttf

4GwpJM7qx9X5Obd9KsnKxQ.ttf

224 ms

zpv3sOKAbMf4wff105oLjw.ttf

zpv3sOKAbMf4wff105oLjw.ttf

79 ms

5pEc4QKTMA2oB4Hi9NkS4w.ttf

5pEc4QKTMA2oB4Hi9NkS4w.ttf

222 ms

AcvTq8Q0lyKKNxRlL28Rn6CWcynf_cDxXwCLxiixG1c.ttf

AcvTq8Q0lyKKNxRlL28Rn6CWcynf_cDxXwCLxiixG1c.ttf

222 ms

XNVd6tsqi9wmKNvnh5HNEKCWcynf_cDxXwCLxiixG1c.ttf

XNVd6tsqi9wmKNvnh5HNEKCWcynf_cDxXwCLxiixG1c.ttf

223 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

277 ms

maps

maps

43 ms

footer_logo.png

footer_logo.png

213 ms

bg-integrity-1.png

bg-integrity-1.png

39 ms

19.jpg

19.jpg

879 ms

48.jpg

48.jpg

600 ms

serve-walkscore-tile.php

serve-walkscore-tile.php

35 ms

_neighborhood-map-bundle_vcnq6kjy.css

_neighborhood-map-bundle_vcnq6kjy.css

211 ms

jquery.min.js

jquery.min.js

176 ms

underscore-min.js

underscore-min.js

179 ms

_tile-start-bundle_vcnq6kjy.js

_tile-start-bundle_vcnq6kjy.js

232 ms

js

js

250 ms

api

api

231 ms

jsapi

jsapi

267 ms

_tile-end-bundle_vcnq6kjy.js

_tile-end-bundle_vcnq6kjy.js

247 ms

embed

embed

881 ms

385 ms

getAllAppDefault.esi

getAllAppDefault.esi

321 ms

gpt.js

gpt.js

43 ms

sprites11.png

sprites11.png

43 ms

progress.gif

progress.gif

42 ms

default+en.I.js

default+en.I.js

10 ms

neighborhood-map-hd_vcnq6kjy.css

neighborhood-map-hd_vcnq6kjy.css

35 ms

pubads_impl_82.js

pubads_impl_82.js

35 ms

27 ms

container.html

container.html

14 ms

ui+en.css

ui+en.css

6 ms

format+en,default+en,ui+en,browserchart+en,columnchart+en_US.I.js

format+en,default+en,ui+en,browserchart+en,columnchart+en_US.I.js

14 ms

analytics.js

analytics.js

47 ms

amenity_map_auth

amenity_map_auth

24 ms

common.js

common.js

58 ms

util.js

util.js

81 ms

geocoder.js

geocoder.js

55 ms

getSegment.php

getSegment.php

143 ms

checkOAuth.esi

checkOAuth.esi

86 ms

collect

collect

34 ms

collect

collect

61 ms

collect

collect

31 ms

collect

collect

31 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

15 ms

GeocodeService.Search

GeocodeService.Search

107 ms

t.dhj

t.dhj

7 ms

t.dhj

t.dhj

8 ms

cm

cm

33 ms

s-3271.xgi

s-3271.xgi

8 ms

8 ms

72 ms

xrefid.xgi

xrefid.xgi

63 ms

map.js

map.js

43 ms

streetview.js

streetview.js

42 ms

get-walkshed.php

get-walkshed.php

149 ms

ads

ads

128 ms

get-data

get-data

75 ms

usage.js

usage.js

71 ms

hbpix

hbpix

68 ms

onion.js

onion.js

88 ms

GeoPhotoService.SingleImageSearch

GeoPhotoService.SingleImageSearch

209 ms

pixel

pixel

56 ms

commute-map_vcnq6kjy.js

commute-map_vcnq6kjy.js

28 ms

js

js

114 ms

amenities-by-cid

amenities-by-cid

68 ms

commute_vcnq6kjy.js

commute_vcnq6kjy.js

21 ms

js

js

139 ms

init_embed.js

init_embed.js

165 ms

pixel

pixel

92 ms

wl

wl

260 ms

stats.js

stats.js

66 ms

osd.js

osd.js

53 ms

commute-map_vcnq6kjy.js

commute-map_vcnq6kjy.js

51 ms

2981

2981

22 ms

commute_vcnq6kjy.js

commute_vcnq6kjy.js

5 ms

js

js

7 ms

common.js

common.js

57 ms

map.js

map.js

56 ms

google4.png

google4.png

81 ms

overlay.js

overlay.js

14 ms

util.js

util.js

79 ms

onion.js

onion.js

76 ms

search_impl.js

search_impl.js

80 ms

moth-min.js

moth-min.js

66 ms

grv-jquery-1.8.2.min.446a642fc8237b3799365aee82b1db0c.js

grv-jquery-1.8.2.min.446a642fc8237b3799365aee82b1db0c.js

69 ms

stats.js

stats.js

42 ms

SEO Factors

207pearl.com 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 207pearl.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 207pearl.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

207pearl.com

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