1.5 sec in total
108 ms
1.2 sec
218 ms
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
Representing injured clients against the pharmaceutical & medical device industry for over 30 years. Call 877-LAW-SUIT for a free & confidential case review.
Visit lewissaul.comWe analyzed Lewissaul.com page load time and found that the first response time was 108 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 25% of websites can load faster.
lewissaul.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value8.7 s
1/100
25%
Value7.4 s
28/100
10%
Value2,420 ms
5/100
30%
Value0.111
87/100
15%
Value9.4 s
30/100
10%
108 ms
140 ms
87 ms
103 ms
115 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 (440 ms) belongs to the original domain Lewissaul.com.
Page size can be reduced by 357.9 kB (41%)
873.3 kB
515.4 kB
In fact, the total size of Lewissaul.com main page is 873.3 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. Javascripts take 371.2 kB which makes up the majority of the site volume.
Potential reduce by 206.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 206.1 kB or 85% of the original size.
Potential reduce by 0 B
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.
Potential reduce by 142.6 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 142.6 kB or 38% of the original size.
Potential reduce by 9.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. Lewissaul.com needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 11% of the original size.
Number of requests can be reduced by 33 (75%)
44
11
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.
lewissaul.com
108 ms
lewissaul.com
140 ms
wp-emoji-release.min.js
87 ms
style.min.css
103 ms
classic-themes.min.css
115 ms
layerslider.css
101 ms
css
28 ms
styles.css
93 ms
settings.css
97 ms
style.css
181 ms
css
40 ms
style.css
199 ms
font-awesome.css
196 ms
ilightbox.css
194 ms
animations.css
198 ms
greensock.js
204 ms
jquery.min.js
269 ms
jquery-migrate.min.js
290 ms
layerslider.kreaturamedia.jquery.js
266 ms
layerslider.transitions.js
268 ms
jquery.themepunch.tools.min.js
279 ms
jquery.themepunch.revolution.min.js
283 ms
wp-polyfill-inert.min.js
357 ms
regenerator-runtime.min.js
360 ms
wp-polyfill.min.js
360 ms
index.js
360 ms
comment-reply.min.js
393 ms
main.min.js
424 ms
LewisSaulOneLineLogo.png
238 ms
HomePageCenterSlide_mini.jpg
227 ms
Icon_LatestNews.png
216 ms
Zofran_small_mini.jpg
215 ms
Icon_featured2.png
215 ms
DefectiveHip_small_mini.jpg
214 ms
Icon_featured3.png
307 ms
DefectiveKnee_small_mini.jpg
302 ms
Icon_featured1.png
304 ms
Xarelto_small_mini.jpg
308 ms
unnamed.png
297 ms
LewisSaulLogo_white.png
409 ms
S6uyw4BMUTPHjx4wWw.ttf
143 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
211 ms
S6u8w4BMUTPHh30AXC-v.ttf
224 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
223 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
224 ms
S6u8w4BMUTPHjxsAXC-v.ttf
224 ms
S6u_w4BMUTPHjxsI5wq_Gwfo.ttf
224 ms
fontawesome-webfont.woff
440 ms
FormSubmitButton.png
375 ms
iframe_api
138 ms
icomoon.woff
288 ms
loader.gif
204 ms
www-widgetapi.js
7 ms
shadow-top.png
86 ms
shadow-bottom.png
88 ms
lewissaul.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lewissaul.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
lewissaul.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
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: