3.9 sec in total
190 ms
3.1 sec
549 ms
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.comWe 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.
williamfrancis.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value13.3 s
0/100
25%
Value7.7 s
25/100
10%
Value1,280 ms
18/100
30%
Value0.228
55/100
15%
Value17.7 s
4/100
10%
190 ms
280 ms
459 ms
49 ms
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 size can be reduced by 843.8 kB (19%)
4.4 MB
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.
Potential reduce by 148.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 148.1 kB or 80% of the original size.
Potential reduce by 91.5 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. Williamfrancis images are well optimized though.
Potential reduce by 567.9 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.
Potential reduce by 36.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. 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.
Number of requests can be reduced by 52 (51%)
101
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.
williamfrancis.com
190 ms
www.williamfrancis.com
280 ms
www.williamfrancis.com
459 ms
sdk.js
49 ms
sites.css
86 ms
fancybox.css
43 ms
social-icons.css
47 ms
main_style.css
152 ms
css
100 ms
css
122 ms
css
121 ms
css
121 ms
templateArtifacts.js
221 ms
jquery.min.js
97 ms
stl.js
42 ms
main.js
74 ms
william-francis-blue-graphic_3.png
382 ms
white-graphic_1.png
488 ms
avvo_3_orig.png
531 ms
ncdd.png
549 ms
ocdla.png
532 ms
william-francis-american-inns-of-court-min_1.jpg
473 ms
osbar-min.png
473 ms
plugins.js
620 ms
custom.js
543 ms
89 ms
5-stars-best-attorney_2_orig.png
576 ms
best-lawyer_orig.png
692 ms
criminal-trial_orig.png
693 ms
not-guilty.png
720 ms
william-francis-cross-examination-cover_1_orig.png
721 ms
jail-cover_1_orig.png
801 ms
out-of-jail-cover_orig.png
737 ms
dui-pre-arrest-screening.png
978 ms
woman-arrested-for-dui_orig.png
1015 ms
oregon-flag_orig.png
979 ms
william-francis-on-the-courthouse-steps-cover-cut_1.png
978 ms
ambien-cover.png
978 ms
william-francis-blue-logo.png
951 ms
cards-in-a-row-min.jpeg
1088 ms
93 ms
0sTQzbapM8j.js
31 ms
1e9892c0-6927-4412-9874-1b82801ba47a.woff
905 ms
fa19948e-5e38-4909-b31e-41acd170d6f2.woff
905 ms
f26faddb-86cc-4477-a253-1e1287684336.woff
914 ms
__utm.gif
137 ms
snowday261.js
113 ms
analytics.js
124 ms
96639888.png
1642 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
98 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
97 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
128 ms
gFXtEMCp1m_YzxsBpKl68i3USBnSvpkopQaUR-2r7iU.ttf
134 ms
IQHow_FEYlDC4Gzy_m8fcrOLyRJkM5aLlPlkJMOAyH0.ttf
150 ms
Pru33qjShpZSmG3z6VYwnaCWcynf_cDxXwCLxiixG1c.ttf
134 ms
5M21SdFLkD52QavfmHs6cA.ttf
133 ms
97uahxiqZRoncBaCEI3aW6CWcynf_cDxXwCLxiixG1c.ttf
132 ms
play-icon.png
39 ms
PRmiXeptR36kaC0GEAetxvqEJM-AK1nFUafhVdytxUY.ttf
120 ms
xjAJXh38I15wypJXxuGMBl02b4v3fUxqf9CZJ1qUoIA.ttf
121 ms
PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf
120 ms
cse.js
382 ms
collect
56 ms
collect
43 ms
ga-audiences
24 ms
ga.js
101 ms
snowday262.js
70 ms
quant.js
154 ms
api.js
65 ms
like.php
203 ms
channel.html
21 ms
recaptcha__en.js
28 ms
__utm.gif
11 ms
jsapi
34 ms
generateMap.php
377 ms
rules-p-0dYLvhSGGqUWo.js
96 ms
default+en.css
4 ms
default.css
14 ms
default+en.I.js
38 ms
Iv-bqISgsE7.js
140 ms
lH1ibRl5GKq.png
113 ms
jquery.min.js
82 ms
generateVideo.php
100 ms
async-ads.js
117 ms
googlelogo_lightgrey_46x16dp.png
113 ms
googlelogo_grey_46x15dp.png
61 ms
search_box_icon.png
61 ms
clear.png
95 ms
nav_logo114.png
87 ms
ncdd.png
131 ms
loading-icon.png
42 ms
play-icon.png
37 ms
gradient.png
35 ms
video_1_721.jpg
242 ms
267447_4_0.woff
45 ms
267447_5_0.woff
37 ms
46cf1067-688d-4aab-b0f7-bd942af6efd8.ttf
166 ms
6de0ce4d-9278-467b-b96f-c1f5f0a4c375.ttf
90 ms
63a74598-733c-4d0c-bd91-b01bffcd6e69.ttf
408 ms
js
50 ms
common.js
7 ms
map.js
18 ms
util.js
43 ms
marker.js
43 ms
StaticMapService.GetMapImage
175 ms
onion.js
20 ms
ViewportInfoService.GetViewportInfo
65 ms
controls.js
17 ms
transparent.png
56 ms
css
19 ms
google4.png
39 ms
mapcnt6.png
40 ms
spotlight-poi.png
38 ms
tmapctrl.png
31 ms
tmapctrl4.png
40 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
24 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
24 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
24 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
23 ms
vt
57 ms
vt
60 ms
vt
49 ms
vt
59 ms
vt
29 ms
vt
40 ms
vt
94 ms
AuthenticationService.Authenticate
27 ms
outer.html
13 ms
inner.html
79 ms
williamfrancis.com accessibility score
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
<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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
williamfrancis.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
williamfrancis.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
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.
williamfrancis.com
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: