Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

castlelaw.com

Experienced Joliet Attorneys | Personal Injury Lawyers

Page Load Speed

1.1 sec in total

First Response

175 ms

Resources Loaded

469 ms

Page Rendered

499 ms

castlelaw.com screenshot

About Website

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

Minimizing Risk… Maximizing Return Dystrup Hoster & Jarot, P.C. is now a Member of Castle Law. new name... additional locations... more attorneys... expanded

Visit castlelaw.com

Key Findings

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

Performance Metrics

castlelaw.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.372

28/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

castlelaw.com

175 ms

www.castlelaw.com

128 ms

client-cad152df95dd89380ae47420f07a5945ed6c6a3ef83a311d744c5a7aeb542050.css

45 ms

css

52 ms

0bfc03bb86.js

87 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Castlelaw.com, 50% (16 requests) were made to Cdn.lawlytics.com and 13% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (175 ms) belongs to the original domain Castlelaw.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 83.3 kB (5%)

Content Size

1.6 MB

After Optimization

1.6 MB

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

HTML Optimization

-78%

Potential reduce by 83.3 kB

  • Original 107.1 kB
  • After minification 101.0 kB
  • After compression 23.8 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 83.3 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.4 MB
  • After minification 1.4 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. Castlelaw images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

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

CSS Optimization

-2%

Potential reduce by 29 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 1.3 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. Castlelaw.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (31%)

Requests Now

26

After Optimization

18

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Castlelaw. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

castlelaw.com accessibility score

83

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

castlelaw.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Castlelaw.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 Castlelaw.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 description is not detected on the main page of Castlelaw. 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: