Tools & Wizards About Us
wellswooster.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

wellswooster.com

Bryant Genealogy Home Page - including the ancestral lines of the townsend holbrook evans chapman morse jones trask pond thomas bushnell cook burdin d...

Page Load Speed

622 ms in total

First Response

121 ms

Resources Loaded

224 ms

Page Rendered

277 ms

wellswooster.com screenshot

About Website

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

Home page for Don Bryant's genealogy research. Families came to West Michigan in the mid and late 1800's from Sweden, New York State, Massachusetts, Connecticut and Rhode Island. The New England branc...

Visit wellswooster.com

Key Findings

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

Performance Metrics

wellswooster.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value0.8 s

100/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

wellswooster.com

121 ms

ga.js

5 ms

tabs1011.css

33 ms

flag-sm.jpg

45 ms

__utm.gif

14 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 88% of them (14 requests) were addressed to the original Wellswooster.com, 13% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (121 ms) belongs to the original domain Wellswooster.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 21.2 kB (23%)

Content Size

93.5 kB

After Optimization

72.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-63%

Potential reduce by 20.2 kB

  • Original 32.2 kB
  • After minification 32.0 kB
  • After compression 12.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 20.2 kB or 63% of the original size.

Image Optimization

-2%

Potential reduce by 734 B

  • Original 39.3 kB
  • After minification 38.6 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. Wellswooster images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-5%

Potential reduce by 239 B

  • Original 4.8 kB
  • After minification 4.8 kB
  • After compression 4.6 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. Wellswooster.com has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

15

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wellswooster. According to our analytics all requests are already optimized.

Network Requests Diagram

wellswooster.com

wellswooster.com

121 ms

ga.js

ga.js

5 ms

tabs1011.css

tabs1011.css

33 ms

flag-sm.jpg

flag-sm.jpg

45 ms

__utm.gif

__utm.gif

14 ms

tabbkgnd.jpg

tabbkgnd.jpg

10 ms

mandolin.jpg

mandolin.jpg

10 ms

martin_th.jpg

martin_th.jpg

15 ms

th_t_townsend.gif

th_t_townsend.gif

22 ms

sandy_eva_th.jpg

sandy_eva_th.jpg

17 ms

sflag_small.gif

sflag_small.gif

17 ms

yellowstone_flat_th.jpg

yellowstone_flat_th.jpg

17 ms

yellowstonetrip05_th.jpg

yellowstonetrip05_th.jpg

18 ms

lcearle_portrait.jpg

lcearle_portrait.jpg

39 ms

atabbul1.gif

atabbul1.gif

24 ms

email.gif

email.gif

27 ms

Accessibility Review

wellswooster.com accessibility score

47

Accessibility Issues

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

wellswooster.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

wellswooster.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wellswooster.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 Wellswooster.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

wellswooster.com

Open Graph description is not detected on the main page of Wellswooster. 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: