Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

williamfrancis.com

Criminal Defense Attorney, DUI Lawyer

Page Load Speed

3.9 sec in total

First Response

190 ms

Resources Loaded

3.1 sec

Page Rendered

549 ms

williamfrancis.com screenshot

About Website

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

Attorney and Lawyer, Criminal Defense and DUI

Visit williamfrancis.com

Key Findings

We analyzed Williamfrancis.com page load time and found that the first response time was 190 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

williamfrancis.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.228

55/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

williamfrancis.com

190 ms

www.williamfrancis.com

280 ms

www.williamfrancis.com

459 ms

sdk.js

49 ms

sites.css

86 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 28% of them (36 requests) were addressed to the original Williamfrancis.com, 13% (17 requests) were made to Maps.googleapis.com and 12% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Williamfrancis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 843.8 kB (19%)

Content Size

4.4 MB

After Optimization

3.6 MB

In fact, the total size of Williamfrancis.com main page is 4.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 148.1 kB

  • Original 184.5 kB
  • After minification 182.4 kB
  • After compression 36.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 148.1 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 91.5 kB

  • Original 3.0 MB
  • After minification 2.9 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. Williamfrancis images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 567.9 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 560.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 567.9 kB or 50% of the original size.

CSS Optimization

-46%

Potential reduce by 36.3 kB

  • Original 78.3 kB
  • After minification 74.3 kB
  • After compression 42.1 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. Williamfrancis.com needs all CSS files to be minified and compressed as it can save up to 36.3 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (51%)

Requests Now

101

After Optimization

49

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

Accessibility Review

williamfrancis.com accessibility score

96

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

<frame> or <iframe> elements do not have a title

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

williamfrancis.com best practices score

75

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

williamfrancis.com SEO score

85

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Williamfrancis.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Williamfrancis.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 data is detected on the main page of Williamfrancis. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: