Tools & Wizards About Us
ellislaw.us screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    90% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

ellislaw.us

Stillwater Estate Planning Attorney | Tax Planning | Asset Protection

Page Load Speed

3.4 sec in total

First Response

438 ms

Resources Loaded

1.9 sec

Page Rendered

1 sec

ellislaw.us screenshot

About Website

Visit ellislaw.us now to see the best up-to-date Ellislaw content and also check out these interesting facts you probably never knew about ellislaw.us

The Stillwater estate planning lawyers of Ellis & Ellis help families and businesses across Payne County and beyond. Call 405-334-5378 for a consultation.

Visit ellislaw.us

Key Findings

We analyzed Ellislaw.us page load time and found that the first response time was 438 ms and then it took 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

ellislaw.us performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value3.1 s

92/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.073

96/100

15%

TTI (Time to Interactive)

Value6.1 s

64/100

10%

Network Requests Diagram

www.ellislaw.us

438 ms

7187caa05c55c146a287bba48c18c39dfba87942a06c080b9c9f7014813ce1a8.js

520 ms

launch-4b8eab27482e.min.js

95 ms

v84a3a4012de94ce1a686ba8c167c359c1696973893317

298 ms

EllisEllis-site-logo.png

488 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 86% of them (43 requests) were addressed to the original Ellislaw.us, 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 (723 ms) belongs to the original domain Ellislaw.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 101.8 kB (28%)

Content Size

367.4 kB

After Optimization

265.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ellislaw.us main page is 367.4 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. 70% of websites need less resources to load. Images take 144.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 101.5 kB

  • Original 127.6 kB
  • After minification 127.6 kB
  • After compression 26.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. 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 101.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-0%

Potential reduce by 291 B

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

Requests Breakdown

Number of requests can be reduced by 5 (21%)

Requests Now

24

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ellislaw.us

www.ellislaw.us

438 ms

7187caa05c55c146a287bba48c18c39dfba87942a06c080b9c9f7014813ce1a8.js

7187caa05c55c146a287bba48c18c39dfba87942a06c080b9c9f7014813ce1a8.js

520 ms

launch-4b8eab27482e.min.js

launch-4b8eab27482e.min.js

95 ms

v84a3a4012de94ce1a686ba8c167c359c1696973893317

v84a3a4012de94ce1a686ba8c167c359c1696973893317

298 ms

EllisEllis-site-logo.png

EllisEllis-site-logo.png

488 ms

home_banner.jpg

home_banner.jpg

288 ms

attorneys-home_banner.png

attorneys-home_banner.png

532 ms

prac-3.png

prac-3.png

472 ms

prac-4.png

prac-4.png

482 ms

prac-1.png

prac-1.png

481 ms

EdmonLowNew.jpg

EdmonLowNew.jpg

544 ms

ThetaPond.jpg

ThetaPond.jpg

592 ms

ThetaPondNew.jpg

ThetaPondNew.jpg

546 ms

Hal-Ellis.jpg

Hal-Ellis.jpg

543 ms

Leann-Drummond-Ellis.jpg

Leann-Drummond-Ellis.jpg

542 ms

quote-3.png

quote-3.png

543 ms

badges-SuperLawyers.png

badges-SuperLawyers.png

642 ms

badges-ACTEC.png

badges-ACTEC.png

652 ms

badges-AV-Rated.png

badges-AV-Rated.png

662 ms

map.png

map.png

723 ms

map.jpg

map.jpg

651 ms

id

id

332 ms

EX3c3542d266c4483894170527bc8a6430-libraryCode_source.min.js

EX3c3542d266c4483894170527bc8a6430-libraryCode_source.min.js

323 ms

AppMeasurement_Module_AudienceManagement.min.js

AppMeasurement_Module_AudienceManagement.min.js

331 ms

dialog-tech.js

dialog-tech.js

111 ms

datadog-rum-v5.js

datadog-rum-v5.js

78 ms

modules.woff

modules.woff

161 ms

css

css

202 ms

s71042603959795

s71042603959795

30 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

96 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

96 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

59 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

58 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

93 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

48 ms

LDIqapSCOBt_aeQQ7ftydoa0reHelJox.ttf

LDIqapSCOBt_aeQQ7ftydoa0reHelJox.ttf

118 ms

LDI1apSCOBt_aeQQ7ftydoa8XsLO.ttf

LDI1apSCOBt_aeQQ7ftydoa8XsLO.ttf

156 ms

LDIqapSCOBt_aeQQ7ftydoa09eDelJox.ttf

LDIqapSCOBt_aeQQ7ftydoa09eDelJox.ttf

159 ms

LDIqapSCOBt_aeQQ7ftydoa0kePelJox.ttf

LDIqapSCOBt_aeQQ7ftydoa0kePelJox.ttf

118 ms

LDIqapSCOBt_aeQQ7ftydoa0gebelJox.ttf

LDIqapSCOBt_aeQQ7ftydoa0gebelJox.ttf

182 ms

LDIqapSCOBt_aeQQ7ftydoa05efelJox.ttf

LDIqapSCOBt_aeQQ7ftydoa05efelJox.ttf

202 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

156 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

190 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

158 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

201 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

202 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

245 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

264 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

264 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

202 ms

Accessibility Review

ellislaw.us accessibility score

97

Accessibility Issues

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

Links do not have a discernible name

Best Practices

ellislaw.us 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

ellislaw.us SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Ellislaw.us 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 Ellislaw.us 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

ellislaw.us

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