Tools & Wizards About Us
stanprowse.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

stanprowse.com

Carlsbad Real Estate Attorney Stanley Prowse Civil Litigation Lawyer

Page Load Speed

2.5 sec in total

First Response

140 ms

Resources Loaded

2 sec

Page Rendered

342 ms

stanprowse.com screenshot

About Website

Click here to check amazing Stan Prowse content for United States. Otherwise, check out these important facts you probably never knew about stanprowse.com

Carlsbad Real Estate Attorney Stan Prowse is a Certified Family Lawyer serving as a Civil Litigation Attorney, Business Lawyer and Divorce Attorney.

Visit stanprowse.com

Key Findings

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

Performance Metrics

stanprowse.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value990 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

stanprowse.com

140 ms

stanprowse.com

450 ms

stylesheet_combined_78cb226a45c406ee58f97fcb721ab92e.css

54 ms

stylesheet_combined_6eb0a812fafba7bbcdce8ae02dff42a8.css

107 ms

settings.css

158 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 69% of them (58 requests) were addressed to the original Stanprowse.com, 6% (5 requests) were made to Youtube.com and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (822 ms) belongs to the original domain Stanprowse.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 192.0 kB (4%)

Content Size

4.3 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 51.0 kB

  • Original 66.6 kB
  • After minification 63.7 kB
  • After compression 15.6 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 51.0 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 131.8 kB

  • Original 3.8 MB
  • After minification 3.6 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. Stan Prowse images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 4.5 kB

  • Original 393.5 kB
  • After minification 393.5 kB
  • After compression 389.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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 4.7 kB

  • Original 98.8 kB
  • After minification 98.8 kB
  • After compression 94.2 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. Stanprowse.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

70

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stanprowse.com

stanprowse.com

140 ms

stanprowse.com

stanprowse.com

450 ms

stylesheet_combined_78cb226a45c406ee58f97fcb721ab92e.css

stylesheet_combined_78cb226a45c406ee58f97fcb721ab92e.css

54 ms

stylesheet_combined_6eb0a812fafba7bbcdce8ae02dff42a8.css

stylesheet_combined_6eb0a812fafba7bbcdce8ae02dff42a8.css

107 ms

settings.css

settings.css

158 ms

layers.css

layers.css

163 ms

navigation.css

navigation.css

161 ms

settings.css

settings.css

168 ms

jquery.js

jquery.js

214 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

213 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

209 ms

css

css

36 ms

badges-v2.js

badges-v2.js

142 ms

conversion.js

conversion.js

88 ms

Prowse-Header-Logo.jpg

Prowse-Header-Logo.jpg

118 ms

08709-Litigation-Home2.jpg

08709-Litigation-Home2.jpg

524 ms

c964f-Couple-Home3.jpg

c964f-Couple-Home3.jpg

649 ms

ccce2-Prowse-CitySkyline2.jpg

ccce2-Prowse-CitySkyline2.jpg

646 ms

b2e79-Construction-Lawyer.jpg

b2e79-Construction-Lawyer.jpg

651 ms

MenuBack.png

MenuBack.png

75 ms

ultoprt.png

ultoprt.png

118 ms

Extended-Handshake.jpg

Extended-Handshake.jpg

176 ms

five-stars.png

five-stars.png

175 ms

google+.jpg

google+.jpg

245 ms

quotes.jpg

quotes.jpg

246 ms

quote-end.jpg

quote-end.jpg

523 ms

TypicalForeclosure-17807706.jpg

TypicalForeclosure-17807706.jpg

522 ms

Civil-Litigation-Attorney.jpg

Civil-Litigation-Attorney.jpg

548 ms

Business-Law-Specialist.jpg

Business-Law-Specialist.jpg

643 ms

FamilyFight.jpg

FamilyFight.jpg

642 ms

Divorce-Mediate.jpg

Divorce-Mediate.jpg

646 ms

Child-Suport.jpg

Child-Suport.jpg

646 ms

Facebook.png

Facebook.png

647 ms

Twitter.png

Twitter.png

663 ms

Google+.png

Google+.png

663 ms

Tumblr.png

Tumblr.png

664 ms

Pocket.png

Pocket.png

664 ms

LinkedIn.png

LinkedIn.png

665 ms

Wordpress.png

Wordpress.png

665 ms

Pinboard.png

Pinboard.png

784 ms

Email.png

Email.png

785 ms

PodCast.png

PodCast.png

786 ms

wordpress.png

wordpress.png

786 ms

feed.png

feed.png

786 ms

f.png

f.png

787 ms

in.png

in.png

787 ms

GooglePlus.png

GooglePlus.png

788 ms

Twitter2.png

Twitter2.png

788 ms

Futura-Medium.woff

Futura-Medium.woff

822 ms

MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf

MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf

53 ms

font

font

102 ms

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

72 ms

DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf

DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf

113 ms

hmr1wli4GHA

hmr1wli4GHA

155 ms

widgets.js

widgets.js

61 ms

sanfranciscodisplay-regular-webfont.woff

sanfranciscodisplay-regular-webfont.woff

594 ms

53 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

690 ms

revolution.extension.actions.min.js

revolution.extension.actions.min.js

691 ms

286071

286071

25 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

692 ms

revolution.extension.navigation.min.js

revolution.extension.navigation.min.js

694 ms

loading_84px_bgFFFFFF.gif

loading_84px_bgFFFFFF.gif

53 ms

94 ms

www-player.css

www-player.css

21 ms

www-embed-player.js

www-embed-player.js

56 ms

base.js

base.js

84 ms

ad_status.js

ad_status.js

165 ms

RudQRherZ_nTCQg2xV6CXD6POZ8OKQrsE859yUgfkYA.js

RudQRherZ_nTCQg2xV6CXD6POZ8OKQrsE859yUgfkYA.js

84 ms

embed.js

embed.js

39 ms

id

id

21 ms

Create

Create

44 ms

GenerateIT

GenerateIT

18 ms

javascript_combined_1646fcf368d81f4e5e663652747c4d3f.js

javascript_combined_1646fcf368d81f4e5e663652747c4d3f.js

63 ms

108 ms

Futura-Medium.ttf

Futura-Medium.ttf

131 ms

coloredbg.png

coloredbg.png

58 ms

loader.gif

loader.gif

58 ms

revicons.woff

revicons.woff

58 ms

revicons.woff

revicons.woff

146 ms

ga.js

ga.js

18 ms

__utm.gif

__utm.gif

15 ms

Futura-Medium.svg

Futura-Medium.svg

129 ms

revicons.ttf

revicons.ttf

132 ms

Accessibility Review

stanprowse.com accessibility score

85

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

Links do not have a discernible name

Best Practices

stanprowse.com best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

stanprowse.com SEO score

92

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stanprowse.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 Stanprowse.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

stanprowse.com

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