Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

johnjstanton.com

Fullerton Estate Planning Attorney | Wills & Trusts | Probate Lawyer

Page Load Speed

2.3 sec in total

First Response

388 ms

Resources Loaded

1.5 sec

Page Rendered

425 ms

johnjstanton.com screenshot

About Website

Welcome to johnjstanton.com homepage info - get ready to check Johnjstanton best content right away, or after learning these important things about johnjstanton.com

At The Law Office of John J. Stanton in Fullerton, we are focused on serving the estate planning and family law needs of our community. Call 714-947-8941.

Visit johnjstanton.com

Key Findings

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

Performance Metrics

johnjstanton.com performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

97/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value7.3 s

49/100

10%

Network Requests Diagram

www.johnjstanton.com

388 ms

Horizontal-Logo.png

185 ms

banner.jpg

281 ms

john-stanton-cutout.png

191 ms

texture.png

199 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 78% of them (35 requests) were addressed to the original Johnjstanton.com, 4% (2 requests) were made to Assets.adobedtm.com and 4% (2 requests) were made to Attorneys.findlaw.com. The less responsive or slowest element that took the longest time to load (533 ms) belongs to the original domain Johnjstanton.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 138.5 kB (40%)

Content Size

346.1 kB

After Optimization

207.6 kB

In fact, the total size of Johnjstanton.com main page is 346.1 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. 60% of websites need less resources to load. HTML takes 150.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 121.8 kB

  • Original 150.8 kB
  • After minification 150.7 kB
  • After compression 29.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 121.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 83.4 kB
  • After minification 83.4 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. Johnjstanton images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 16.7 kB

  • Original 111.9 kB
  • After minification 111.9 kB
  • After compression 95.2 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 16.7 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (32%)

Requests Now

22

After Optimization

15

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

Accessibility Review

johnjstanton.com accessibility score

97

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

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

Missing source maps for large first-party JavaScript

SEO Factors

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

    EN

  • Encoding

    UTF-8

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

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