Tools & Wizards About Us
lewissaul.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

lewissaul.com

Lewis Saul & Associates P.C. -

Page Load Speed

1.5 sec in total

First Response

124 ms

Resources Loaded

1.2 sec

Page Rendered

182 ms

lewissaul.com screenshot

About Website

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

Visit lewissaul.com

Key Findings

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

Performance Metrics

lewissaul.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.455

20/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

lewissaul.com

124 ms

lewissaul.com

149 ms

wp-emoji-release.min.js

85 ms

style.min.css

100 ms

classic-themes.min.css

142 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 80% of them (44 requests) were addressed to the original Lewissaul.com, 13% (7 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (537 ms) belongs to the original domain Lewissaul.com.

Page Optimization Overview & Recommendations

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

Content Size

817.9 kB

After Optimization

592.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lewissaul.com main page is 817.9 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. 45% of websites need less resources to load. Javascripts take 344.9 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 195.6 kB

  • Original 231.1 kB
  • After minification 229.8 kB
  • After compression 35.4 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 195.6 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 168.0 kB
  • After minification 168.0 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. Lewis Saul images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 21.9 kB

  • Original 344.9 kB
  • After minification 344.9 kB
  • After compression 323.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

-11%

Potential reduce by 8.4 kB

  • Original 74.0 kB
  • After minification 74.0 kB
  • After compression 65.6 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. Lewissaul.com needs all CSS files to be minified and compressed as it can save up to 8.4 kB or 11% of the original size.

Requests Breakdown

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

Requests Now

44

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lewissaul.com

lewissaul.com

124 ms

lewissaul.com

lewissaul.com

149 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

85 ms

style.min.css

style.min.css

100 ms

classic-themes.min.css

classic-themes.min.css

142 ms

layerslider.css

layerslider.css

117 ms

css

css

30 ms

styles.css

styles.css

109 ms

settings.css

settings.css

114 ms

style.css

style.css

181 ms

css

css

58 ms

style.css

style.css

178 ms

font-awesome.css

font-awesome.css

195 ms

ilightbox.css

ilightbox.css

204 ms

animations.css

animations.css

209 ms

greensock.js

greensock.js

315 ms

jquery.min.js

jquery.min.js

341 ms

jquery-migrate.min.js

jquery-migrate.min.js

331 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

353 ms

layerslider.transitions.js

layerslider.transitions.js

351 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

311 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

416 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

397 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

455 ms

wp-polyfill.min.js

wp-polyfill.min.js

456 ms

index.js

index.js

456 ms

comment-reply.min.js

comment-reply.min.js

456 ms

main.min.js

main.min.js

537 ms

LewisSaulOneLineLogo.png

LewisSaulOneLineLogo.png

182 ms

HomePageCenterSlide_mini.jpg

HomePageCenterSlide_mini.jpg

182 ms

Icon_LatestNews.png

Icon_LatestNews.png

105 ms

Zofran_small_mini.jpg

Zofran_small_mini.jpg

110 ms

Icon_featured2.png

Icon_featured2.png

232 ms

DefectiveHip_small_mini.jpg

DefectiveHip_small_mini.jpg

249 ms

Icon_featured3.png

Icon_featured3.png

248 ms

DefectiveKnee_small_mini.jpg

DefectiveKnee_small_mini.jpg

249 ms

Icon_featured1.png

Icon_featured1.png

248 ms

Xarelto_small_mini.jpg

Xarelto_small_mini.jpg

248 ms

unnamed.png

unnamed.png

248 ms

LewisSaulLogo_white.png

LewisSaulLogo_white.png

414 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

65 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

76 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

153 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

203 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

204 ms

S6u8w4BMUTPHjxsAXC-v.ttf

S6u8w4BMUTPHjxsAXC-v.ttf

204 ms

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

203 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

386 ms

FormSubmitButton.png

FormSubmitButton.png

273 ms

icomoon.woff

icomoon.woff

317 ms

iframe_api

iframe_api

93 ms

loader.gif

loader.gif

84 ms

www-widgetapi.js

www-widgetapi.js

4 ms

shadow-top.png

shadow-top.png

78 ms

shadow-bottom.png

shadow-bottom.png

93 ms

Accessibility Review

lewissaul.com accessibility score

71

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lewissaul.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

lewissaul.com SEO score

76

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

High

Image elements do not have [alt] attributes

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

    EN

  • Encoding

    UTF-8

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

lewissaul.com

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