Tools & Wizards About Us
call811.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

call811.com

Call 811 - Know what's below. Call before you dig.

Page Load Speed

2.4 sec in total

First Response

352 ms

Resources Loaded

1.5 sec

Page Rendered

621 ms

call811.com screenshot

About Website

Visit call811.com now to see the best up-to-date Call 811 content for United States and also check out these interesting facts you probably never knew about call811.com

Anyone who plans to dig should call 811 or go to their state 811 center’s website to request the approximate location of buried utilities be marked.

Visit call811.com

Key Findings

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

Performance Metrics

call811.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

call811.com

352 ms

call811.com

334 ms

sp.js

43 ms

css

26 ms

js

313 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 82% of them (32 requests) were addressed to the original Call811.com, 5% (2 requests) were made to Googletagmanager.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (381 ms) belongs to the original domain Call811.com.

Page Optimization Overview & Recommendations

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

Content Size

4.4 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Call811.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 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 120.3 kB

  • Original 173.7 kB
  • After minification 161.4 kB
  • After compression 53.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 120.3 kB or 69% of the original size.

Image Optimization

-7%

Potential reduce by 291.0 kB

  • Original 4.2 MB
  • After minification 3.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. Call 811 images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 5.5 kB

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

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 7.4 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.

Requests Breakdown

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

Requests Now

32

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

call811.com

call811.com

352 ms

call811.com

call811.com

334 ms

sp.js

sp.js

43 ms

css

css

26 ms

js

js

313 ms

js

js

57 ms

WebResource.axd

WebResource.axd

378 ms

ScriptResource.axd

ScriptResource.axd

381 ms

ScriptResource.axd

ScriptResource.axd

377 ms

js

js

308 ms

css

css

40 ms

js

js

44 ms

CGA-Logo-Sting-v5.gif

CGA-Logo-Sting-v5.gif

32 ms

Asset%201.png

Asset%201.png

41 ms

shovel-i1.gif

shovel-i1.gif

33 ms

shovel-i2.gif

shovel-i2.gif

34 ms

i-stack-i1.gif

i-stack-i1.gif

41 ms

i-stack-i2.gif

i-stack-i2.gif

43 ms

icons_0003_hardhat-grey.png

icons_0003_hardhat-grey.png

42 ms

icons_0004_hardhat.png

icons_0004_hardhat.png

41 ms

icons_0007_plans-grey.png

icons_0007_plans-grey.png

66 ms

icons_0008_plans.png

icons_0008_plans.png

67 ms

icons_0005_shovel-grey.png

icons_0005_shovel-grey.png

69 ms

icons_0006_shovel.png

icons_0006_shovel.png

66 ms

family-home-min.png

family-home-min.png

69 ms

hp2construction-min.png

hp2construction-min.png

67 ms

CGA-logo.png

CGA-logo.png

69 ms

js

js

87 ms

analytics.js

analytics.js

82 ms

ground.jpg

ground.jpg

71 ms

iStock_6-grad.png

iStock_6-grad.png

194 ms

shovel-home.png

shovel-home.png

68 ms

font

font

135 ms

HelveticaNeue-CondensedBlack.woff

HelveticaNeue-CondensedBlack.woff

117 ms

fa-solid-900.woff

fa-solid-900.woff

299 ms

fa-regular-400.woff

fa-regular-400.woff

288 ms

fa-brands-400.woff

fa-brands-400.woff

120 ms

collect

collect

23 ms

main.js

main.js

20 ms

Accessibility Review

call811.com accessibility score

90

Accessibility Issues

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.

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

call811.com best practices score

83

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

SEO Factors

call811.com SEO score

93

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

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

call811.com

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