Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

williamslakefront.com

Williams Lakefront Construction | Custom Boat Docks | Boat Floater

Page Load Speed

2.6 sec in total

First Response

102 ms

Resources Loaded

2.4 sec

Page Rendered

84 ms

williamslakefront.com screenshot

About Website

Visit williamslakefront.com now to see the best up-to-date Williams Lakefront content and also check out these interesting facts you probably never knew about williamslakefront.com

Williams Lakefront Construction specializes in the fabrication of our own customized galvanized steel frame docks, aluminum docks, and poly docks.

Visit williamslakefront.com

Key Findings

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

Performance Metrics

williamslakefront.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value13.0 s

12/100

10%

Network Requests Diagram

www.williamslakefront.com

102 ms

minified.js

33 ms

focus-within-polyfill.js

26 ms

polyfill.min.js

103 ms

thunderbolt-commons.ec68bee9.bundle.min.js

14 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Williamslakefront.com, 53% (43 requests) were made to Static.wixstatic.com and 27% (22 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 330.7 kB (16%)

Content Size

2.1 MB

After Optimization

1.8 MB

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

HTML Optimization

-76%

Potential reduce by 300.8 kB

  • Original 394.8 kB
  • After minification 393.2 kB
  • After compression 94.0 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 300.8 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 27.2 kB

  • Original 1.5 MB
  • After minification 1.5 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. Williams Lakefront images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.7 kB

  • Original 228.3 kB
  • After minification 228.3 kB
  • After compression 225.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.

Requests Breakdown

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

Requests Now

58

After Optimization

48

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Williams Lakefront. 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.

Accessibility Review

williamslakefront.com accessibility score

89

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

button, link, and menuitem elements do not have accessible names.

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

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.

Best Practices

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

High

Page has valid source maps

SEO Factors

williamslakefront.com SEO score

98

Search Engine Optimization Advices

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 Williamslakefront.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 Williamslakefront.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 Williams Lakefront. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: