Tools & Wizards About Us
briggswholey.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

briggswholey.com

Briggs & Wholey | Personal Injury Attorneys Serving All of Maine

Page Load Speed

4 sec in total

First Response

43 ms

Resources Loaded

3.8 sec

Page Rendered

197 ms

briggswholey.com screenshot

About Website

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

Experience and results when you need us the most. We are statewide trial attorneys in Maine. We specialize in personal injury from medical malpractice to car accidents to wrongful death. Contact us to...

Visit briggswholey.com

Key Findings

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

Performance Metrics

briggswholey.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value190 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

briggswholey.com

43 ms

www.maine-personal-injury-lawyers.com

805 ms

style.min.css

43 ms

dashicons.min.css

105 ms

jquery.fancybox.min.css

63 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Briggswholey.com, 81% (57 requests) were made to Maine-personal-injury-lawyers.com and 11% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Maine-personal-injury-lawyers.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.7 kB (17%)

Content Size

577.7 kB

After Optimization

482.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Briggswholey.com main page is 577.7 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. 45% of websites need less resources to load. Images take 246.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 49.5 kB

  • Original 62.1 kB
  • After minification 58.4 kB
  • After compression 12.6 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 49.5 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 18.5 kB

  • Original 246.0 kB
  • After minification 227.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. Briggs Wholey images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 15.6 kB

  • Original 172.0 kB
  • After minification 171.8 kB
  • After compression 156.4 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

-12%

Potential reduce by 12.1 kB

  • Original 97.6 kB
  • After minification 96.6 kB
  • After compression 85.5 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. Briggswholey.com needs all CSS files to be minified and compressed as it can save up to 12.1 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (82%)

Requests Now

44

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

briggswholey.com

briggswholey.com

43 ms

www.maine-personal-injury-lawyers.com

www.maine-personal-injury-lawyers.com

805 ms

style.min.css

style.min.css

43 ms

dashicons.min.css

dashicons.min.css

105 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

63 ms

sassy-social-share-public.css

sassy-social-share-public.css

64 ms

style.css

style.css

70 ms

fontawesome-all.min.css

fontawesome-all.min.css

74 ms

slick.css

slick.css

72 ms

slick-theme.css

slick-theme.css

84 ms

featherlight.min.css

featherlight.min.css

85 ms

jquery.mmenu.all.css

jquery.mmenu.all.css

94 ms

jquery.mmenu.positioning.css

jquery.mmenu.positioning.css

636 ms

jquery.mmenu.setselected.css

jquery.mmenu.setselected.css

723 ms

jquery.mhead.css

jquery.mhead.css

104 ms

hamburgers.min.css

hamburgers.min.css

106 ms

css

css

33 ms

jquery.min.js

jquery.min.js

142 ms

jquery-migrate.min.js

jquery-migrate.min.js

124 ms

modernizr.custom.min.js

modernizr.custom.min.js

125 ms

js

js

64 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

117 ms

sassy-social-share-public.js

sassy-social-share-public.js

167 ms

scripts.js

scripts.js

138 ms

slick.min.js

slick.min.js

141 ms

tabs.js

tabs.js

153 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

162 ms

inview.min.js

inview.min.js

162 ms

featherlight.min.js

featherlight.min.js

177 ms

jquery.mmenu.all.js

jquery.mmenu.all.js

209 ms

jquery.mmenu.setselected.js

jquery.mmenu.setselected.js

184 ms

jquery.mhead.js

jquery.mhead.js

189 ms

ilnksrvr.aspx

ilnksrvr.aspx

170 ms

defaults.css

defaults.css

146 ms

base.css

base.css

154 ms

640.css

640.css

160 ms

768.css

768.css

170 ms

1024.css

1024.css

175 ms

1240.css

1240.css

178 ms

grid.css

grid.css

182 ms

retina.css

retina.css

194 ms

print.css

print.css

195 ms

logo@2x.png

logo@2x.png

92 ms

720

720

796 ms

overlayBG.png

overlayBG.png

92 ms

101

101

605 ms

98

98

814 ms

102

102

957 ms

671

671

805 ms

673

673

1255 ms

669

669

1431 ms

resultsBG.png

resultsBG.png

856 ms

157

157

1452 ms

callout2_BG.png

callout2_BG.png

938 ms

chat-person.png

chat-person.png

897 ms

socmed.png

socmed.png

939 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

99 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

98 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

115 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

126 ms

fa-regular-400.woff

fa-regular-400.woff

889 ms

fa-light-300.woff

fa-light-300.woff

908 ms

fa-solid-900.woff

fa-solid-900.woff

948 ms

EJRVQgYoZZY2vCFuvAFWzro.ttf

EJRVQgYoZZY2vCFuvAFWzro.ttf

126 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

126 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

141 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

126 ms

wARDj0u

wARDj0u

1 ms

submenuBG.png

submenuBG.png

1431 ms

ajax-loader.gif

ajax-loader.gif

1383 ms

Accessibility Review

briggswholey.com accessibility score

70

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not have valid values

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

briggswholey.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

briggswholey.com SEO score

83

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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

briggswholey.com

Open Graph data is detected on the main page of Briggs Wholey. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: