Tools & Wizards About Us
davidandpei.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

davidandpei.com

Pasadena Homes For Sale Pasadena Real Estate CA David Lao & Pei Chang

Page Load Speed

3.5 sec in total

First Response

220 ms

Resources Loaded

2.6 sec

Page Rendered

662 ms

davidandpei.com screenshot

About Website

Welcome to davidandpei.com homepage info - get ready to check David And Pei best content right away, or after learning these important things about davidandpei.com

Pasadena Real Estate, Altadena Homes For Sale, CA Houses, San Marino Realty, Los Angeles Properties, South Pasadena Townhomes, Los Angeles Land by Realtor David Lao & Pei Chang

Visit davidandpei.com

Key Findings

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

Performance Metrics

davidandpei.com performance score

0

Network Requests Diagram

davidandpei.com

220 ms

www.davidandpei.com

307 ms

jquery.js

269 ms

jquery.validity.js

189 ms

SessionService.js

172 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 77% of them (43 requests) were addressed to the original Davidandpei.com, 14% (8 requests) were made to Fonts.gstatic.com and 9% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Davidandpei.com.

Page Optimization Overview & Recommendations

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

Content Size

5.7 MB

After Optimization

5.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 63.5 kB

  • Original 79.5 kB
  • After minification 77.3 kB
  • After compression 16.0 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 63.5 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 217.5 kB

  • Original 5.5 MB
  • After minification 5.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. David And Pei images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 9.2 kB

  • Original 66.3 kB
  • After minification 66.3 kB
  • After compression 57.0 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 9.2 kB or 14% of the original size.

CSS Optimization

-35%

Potential reduce by 24.9 kB

  • Original 71.8 kB
  • After minification 71.1 kB
  • After compression 46.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. Davidandpei.com needs all CSS files to be minified and compressed as it can save up to 24.9 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (58%)

Requests Now

45

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

davidandpei.com

davidandpei.com

220 ms

www.davidandpei.com

www.davidandpei.com

307 ms

jquery.js

jquery.js

269 ms

jquery.validity.js

jquery.validity.js

189 ms

SessionService.js

SessionService.js

172 ms

popUp.js

popUp.js

187 ms

loginModule.js

loginModule.js

173 ms

_Login_01.css

_Login_01.css

260 ms

_Thank_You_01.css

_Thank_You_01.css

315 ms

jquery.modal.css

jquery.modal.css

314 ms

supersized.css

supersized.css

396 ms

supersized.shutter.css

supersized.shutter.css

397 ms

DropdownMenu.css

DropdownMenu.css

409 ms

AT_Styles.css

AT_Styles.css

423 ms

D_Styles.css

D_Styles.css

529 ms

_IDX_search.css

_IDX_search.css

456 ms

g_styles.css

g_styles.css

566 ms

_Quick_Search.css

_Quick_Search.css

547 ms

base.min.css

base.min.css

672 ms

base.min.js

base.min.js

601 ms

jquery.easing.min.js

jquery.easing.min.js

602 ms

supersized.3.2.7.min.js

supersized.3.2.7.min.js

692 ms

supersized.shutter.min.js

supersized.shutter.min.js

693 ms

validateForm.js

validateForm.js

714 ms

index.mobile.js

index.mobile.js

749 ms

css

css

33 ms

css

css

24 ms

css

css

46 ms

css

css

45 ms

css

css

45 ms

getLead

getLead

168 ms

smico_facebook.png

smico_facebook.png

188 ms

smico_yelp.png

smico_yelp.png

206 ms

125307_8262019124141PM64973.jpg

125307_8262019124141PM64973.jpg

529 ms

125307_98201734448PM27420.jpg

125307_98201734448PM27420.jpg

462 ms

qs-bg.png

qs-bg.png

182 ms

btn-search-trans.png

btn-search-trans.png

320 ms

CFSS002.png

CFSS002.png

467 ms

CFSS003.png

CFSS003.png

535 ms

CFSS001.png

CFSS001.png

532 ms

border-image.png

border-image.png

461 ms

RL01.gif

RL01.gif

537 ms

RL02.gif

RL02.gif

602 ms

logo1.png

logo1.png

604 ms

125307_98201743920PM64803.JPG

125307_98201743920PM64803.JPG

1262 ms

125307_98201743318PM59624.jpg

125307_98201743318PM59624.jpg

1191 ms

125307_98201743318PM21353.jpg

125307_98201743318PM21353.jpg

1204 ms

progress.gif

progress.gif

691 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

13 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

66 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

25 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

76 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

77 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

43 ms

tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf

tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf

44 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RkBI96.ttf

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RkBI96.ttf

44 ms

SEO Factors

davidandpei.com SEO score

0

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

davidandpei.com

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