Tools & Wizards About Us
aigensoc.org screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

aigensoc.org

Amelia Island Genealogical Society — Amelia Island Genealogical Society

Page Load Speed

1.4 sec in total

First Response

67 ms

Resources Loaded

524 ms

Page Rendered

796 ms

aigensoc.org screenshot

About Website

Welcome to aigensoc.org homepage info - get ready to check Aigensoc best content right away, or after learning these important things about aigensoc.org

For over a quarter of a century the Amelia Island Genealogical Society (AIGS) has been proud to serve both those seeking information about Amelia Island

Visit aigensoc.org

Key Findings

We analyzed Aigensoc.org page load time and found that the first response time was 67 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

aigensoc.org performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

79/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value2.7 s

97/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.298

40/100

15%

TTI (Time to Interactive)

Value3.7 s

91/100

10%

Network Requests Diagram

aigensoc.org

67 ms

aigensoc.org

149 ms

frontend.min.css

47 ms

style.min.css

66 ms

mediaelementplayer-legacy.min.css

71 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 95% of them (36 requests) were addressed to the original Aigensoc.org, 3% (1 request) were made to Googletagmanager.com and 3% (1 request) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (203 ms) belongs to the original domain Aigensoc.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 181.7 kB (10%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aigensoc.org main page is 1.7 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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 177.7 kB

  • Original 215.2 kB
  • After minification 211.8 kB
  • After compression 37.5 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 177.7 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.4 MB
  • After minification 1.4 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. Aigensoc images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.5 kB

  • Original 75.0 kB
  • After minification 74.5 kB
  • After compression 73.5 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

-3%

Potential reduce by 2.5 kB

  • Original 70.9 kB
  • After minification 70.9 kB
  • After compression 68.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. Aigensoc.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (78%)

Requests Now

36

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aigensoc.org

aigensoc.org

67 ms

aigensoc.org

aigensoc.org

149 ms

frontend.min.css

frontend.min.css

47 ms

style.min.css

style.min.css

66 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

71 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

71 ms

base.css

base.css

70 ms

variation_1.css

variation_1.css

71 ms

common-style.css

common-style.css

70 ms

custom-style-blocks.css

custom-style-blocks.css

88 ms

lightbox.min.css

lightbox.min.css

99 ms

style.css

style.css

100 ms

jquery.min.js

jquery.min.js

115 ms

jquery-migrate.min.js

jquery-migrate.min.js

99 ms

js

js

75 ms

variables-skeleton.min.css

variables-skeleton.min.css

89 ms

common-skeleton.min.css

common-skeleton.min.css

95 ms

widget-events-list-skeleton.min.css

widget-events-list-skeleton.min.css

99 ms

variables-full.min.css

variables-full.min.css

171 ms

common-full.min.css

common-full.min.css

187 ms

widget-events-list-full.min.css

widget-events-list-full.min.css

189 ms

frontend.min.js

frontend.min.js

196 ms

post.min.js

post.min.js

197 ms

wp-lightbox-2.min.js

wp-lightbox-2.min.js

197 ms

e-202444.js

e-202444.js

17 ms

tribe-common.min.js

tribe-common.min.js

196 ms

query-string.min.js

query-string.min.js

199 ms

underscore-before.js

underscore-before.js

203 ms

underscore.min.js

underscore.min.js

203 ms

underscore-after.js

underscore-after.js

203 ms

manager.min.js

manager.min.js

203 ms

breakpoints.min.js

breakpoints.min.js

203 ms

cropped-BANNER-20210514-Draft-for-Dennis-JPG-581x194.jpg.webp

cropped-BANNER-20210514-Draft-for-Dennis-JPG-581x194.jpg.webp

64 ms

IMG_0650-scaled.jpg

IMG_0650-scaled.jpg

140 ms

1905-Death-Certificate-_____-Cain-996x1024.jpg

1905-Death-Certificate-_____-Cain-996x1024.jpg

138 ms

Angel-Island-Immigration-Station.jpg

Angel-Island-Immigration-Station.jpg

64 ms

1903-Oldsmobile-Runabout.jpg

1903-Oldsmobile-Runabout.jpg

93 ms

The-Nassau-County-Genealogist-cover-e1651098002881-1024x280.jpg.webp

The-Nassau-County-Genealogist-cover-e1651098002881-1024x280.jpg.webp

65 ms

Accessibility Review

aigensoc.org accessibility score

83

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

aigensoc.org best practices score

92

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

SEO Factors

aigensoc.org SEO score

99

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 Aigensoc.org 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 Aigensoc.org 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

aigensoc.org

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