Tools & Wizards About Us

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

williamroam.com

William Roam

Page Load Speed

1.3 sec in total

First Response

139 ms

Resources Loaded

1.1 sec

Page Rendered

105 ms

About Website

Welcome to williamroam.com homepage info - get ready to check William Roam best content for United States right away, or after learning these important things about williamroam.com

Spa-quality, American Made Amenities for your home and hotel

Visit williamroam.com

Key Findings

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

Performance Metrics

williamroam.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value640 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.417

23/100

15%

TTI (Time to Interactive)

Value8.8 s

36/100

10%

Network Requests Diagram

williamroam.com

139 ms

williamroam.com

551 ms

theme-bundle.polyfills.js

352 ms

theme-bundle.head_async.js

82 ms

webfont.js

64 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 9% of them (3 requests) were addressed to the original Williamroam.com, 55% (18 requests) were made to Cdn11.bigcommerce.com and 12% (4 requests) were made to Cdn.shopify.com. The less responsive or slowest element that took the longest time to load (551 ms) belongs to the original domain Williamroam.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.3 kB (11%)

Content Size

1.1 MB

After Optimization

936.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Williamroam.com main page is 1.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 914.4 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 117.7 kB

  • Original 133.9 kB
  • After minification 123.6 kB
  • After compression 16.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 117.7 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 18 B

  • Original 914.4 kB
  • After minification 914.3 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. William Roam images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 565 B

  • Original 6.9 kB
  • After minification 6.9 kB
  • After compression 6.3 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 6 (22%)

Requests Now

27

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

williamroam.com accessibility score

87

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 match their roles

High

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

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

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

Missing source maps for large first-party JavaScript

SEO Factors

williamroam.com SEO score

90

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

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 Williamroam.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 Williamroam.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 description is not detected on the main page of William Roam. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: