Tools & Wizards About Us
richardrshawlaw.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

richardrshawlaw.com

Criminal Attorney Buffalo, NY, Criminal Defense Attorney, Criminal Law Attorney

Page Load Speed

23.8 sec in total

First Response

1.2 sec

Resources Loaded

22.2 sec

Page Rendered

394 ms

richardrshawlaw.com screenshot

About Website

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

Depend on the criminal attorney in Buffalo, NY, with the experience and drive to tackle your case. Don't settle for just any criminal defense attorney.

Visit richardrshawlaw.com

Key Findings

We analyzed Richardrshawlaw.com page load time and found that the first response time was 1.2 sec and then it took 22.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

richardrshawlaw.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

richardrshawlaw.com

1183 ms

analytics.js

30 ms

jquery.js

49 ms

button.css

49 ms

browserBehavior.js

62 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 22% of them (17 requests) were addressed to the original Richardrshawlaw.com, 56% (43 requests) were made to Assets.myregisteredsite.com and 9% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source 16365967.cstsite.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.6 kB (9%)

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 84.1 kB

  • Original 112.3 kB
  • After minification 111.6 kB
  • After compression 28.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 84.1 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 46.0 kB

  • Original 1.6 MB
  • After minification 1.5 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. Richardrshaw Law images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 29.5 kB

  • Original 135.6 kB
  • After minification 133.4 kB
  • After compression 106.1 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 29.5 kB or 22% of the original size.

CSS Optimization

-15%

Potential reduce by 851 B

  • Original 5.6 kB
  • After minification 5.6 kB
  • After compression 4.7 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. Richardrshawlaw.com needs all CSS files to be minified and compressed as it can save up to 851 B or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (63%)

Requests Now

59

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

richardrshawlaw.com

richardrshawlaw.com

1183 ms

analytics.js

analytics.js

30 ms

jquery.js

jquery.js

49 ms

button.css

button.css

49 ms

browserBehavior.js

browserBehavior.js

62 ms

utils.js

utils.js

100 ms

shared.js

shared.js

47 ms

navigation.js

navigation.js

132 ms

uaDefaultStylesReset.css

uaDefaultStylesReset.css

50 ms

popup.js

popup.js

163 ms

ResourceLoader.js

ResourceLoader.js

50 ms

webcom_copyright.js

webcom_copyright.js

45 ms

collect

collect

19 ms

jquery.js

jquery.js

127 ms

shared.js

shared.js

99 ms

button.css

button.css

100 ms

uaDefaultStylesReset.css

uaDefaultStylesReset.css

100 ms

ResourceLoader.js

ResourceLoader.js

104 ms

webcom_copyright.js

webcom_copyright.js

106 ms

webfont.js

webfont.js

11 ms

googleFonts.css

googleFonts.css

27 ms

css

css

22 ms

css

css

36 ms

jquery.js

jquery.js

258 ms

navigation.js

navigation.js

26 ms

core.js

core.js

26 ms

socialmediashare.js

socialmediashare.js

25 ms

jqueryvalidate.js

jqueryvalidate.js

31 ms

form.js

form.js

47 ms

footercontact.js

footercontact.js

43 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

17 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

25 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

22 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

30 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff

23 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff

32 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexg.woff

36 ms

hoverIntent.js

hoverIntent.js

26 ms

bgIframe.js

bgIframe.js

25 ms

superfish.js

superfish.js

25 ms

handler.js

handler.js

26 ms

helper.js

helper.js

27 ms

positioner.js

positioner.js

23 ms

structure.css

structure.css

40 ms

smstemplates.js

smstemplates.js

41 ms

socialmediashare.css

socialmediashare.css

42 ms

utils.js

utils.js

46 ms

resources.js

resources.js

42 ms

templates.js

templates.js

43 ms

form.css

form.css

57 ms

form_generic.css

form_generic.css

57 ms

jquery.json-2.2.min.js

jquery.json-2.2.min.js

58 ms

templates.js

templates.js

56 ms

footercontact.css

footercontact.css

68 ms

115855322.png

115855322.png

20401 ms

115855221.png

115855221.png

43 ms

115858343.png

115858343.png

144 ms

115855737.png

115855737.png

107 ms

115855189.png

115855189.png

110 ms

131639434.png

131639434.png

143 ms

115856607.png

115856607.png

206 ms

115858345.png

115858345.png

188 ms

115858347.png

115858347.png

160 ms

115858349.png

115858349.png

162 ms

Leads_WSP.gif

Leads_WSP.gif

40 ms

115854142.png

115854142.png

99 ms

115857676.jpg

115857676.jpg

583 ms

115855490.png

115855490.png

506 ms

115856909.jpg

115856909.jpg

570 ms

Leads_WSP.gif

Leads_WSP.gif

64 ms

logger.php

logger.php

64 ms

placeholder.png

placeholder.png

32 ms

facebook-color.png

facebook-color.png

29 ms

twitter-color.png

twitter-color.png

33 ms

linkedin-color.png

linkedin-color.png

27 ms

frozen-redirect.html

frozen-redirect.html

1565 ms

logger.php

logger.php

75 ms

Accessibility Review

richardrshawlaw.com accessibility score

94

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

richardrshawlaw.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

richardrshawlaw.com SEO score

98

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

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

richardrshawlaw.com

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