Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

weidner.org

The Weidner & Raupp Families of Buffalo Grove, Lake County, Illinois - Main Page

Page Load Speed

3.8 sec in total

First Response

1.1 sec

Resources Loaded

2.5 sec

Page Rendered

127 ms

weidner.org screenshot

About Website

Visit weidner.org now to see the best up-to-date Weidner content and also check out these interesting facts you probably never knew about weidner.org

The Weidner Research Center is dedicated to researching and preserving the genealogy and history of the Weidner and Raupp families of Buffalo Grove, Illinois and their allied families. This is accompl...

Visit weidner.org

Key Findings

We analyzed Weidner.org page load time and found that the first response time was 1.1 sec and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

weidner.org performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.199

62/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

weidner.org

1149 ms

layout1.css

68 ms

site.css

410 ms

jquery.min.js

737 ms

scripts.js

165 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that all of those requests were addressed to Weidner.org and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Weidner.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.7 kB (14%)

Content Size

188.6 kB

After Optimization

161.9 kB

In fact, the total size of Weidner.org main page is 188.6 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. Only 10% of websites need less resources to load. Images take 103.0 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 2.9 kB

  • Original 4.8 kB
  • After minification 4.7 kB
  • After compression 1.9 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 2.9 kB or 60% of the original size.

Image Optimization

-11%

Potential reduce by 11.1 kB

  • Original 103.0 kB
  • After minification 91.9 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. Obviously, Weidner needs image optimization as it can save up to 11.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-14%

Potential reduce by 10.1 kB

  • Original 70.5 kB
  • After minification 70.5 kB
  • After compression 60.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 10.1 kB or 14% of the original size.

CSS Optimization

-26%

Potential reduce by 2.7 kB

  • Original 10.3 kB
  • After minification 10.2 kB
  • After compression 7.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. Weidner.org needs all CSS files to be minified and compressed as it can save up to 2.7 kB or 26% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

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

Accessibility Review

weidner.org accessibility score

70

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.

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

Best Practices

weidner.org best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

weidner.org SEO score

83

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

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

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weidner.org 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 Weidner.org main page’s claimed encoding is windows-1252. 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

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