Tools & Wizards About Us
gildedage2.omeka.net screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

gildedage2.omeka.net

Documenting the Gilded Age: New York City Exhibitions at the Turn of the 20th Century: Phase II

Page Load Speed

664 ms in total

First Response

146 ms

Resources Loaded

380 ms

Page Rendered

138 ms

gildedage2.omeka.net screenshot

About Website

Visit gildedage2.omeka.net now to see the best up-to-date Gilded Age 2 Omeka content for United States and also check out these interesting facts you probably never knew about gildedage2.omeka.net

This online exhibition represents the second phase of the NYARC Documenting the Gilded Age digitization project.

Visit gildedage2.omeka.net

Key Findings

We analyzed Gildedage2.omeka.net page load time and found that the first response time was 146 ms and then it took 518 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

gildedage2.omeka.net performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.176

68/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

Network Requests Diagram

gildedage2.omeka.net

146 ms

js

123 ms

public.css

2 ms

css

37 ms

iconfonts.css

9 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 60% of them (15 requests) were addressed to the original Gildedage2.omeka.net, 20% (5 requests) were made to D1y502jg6fpugt.cloudfront.net and 8% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (149 ms) relates to the external source D1y502jg6fpugt.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 128.4 kB (41%)

Content Size

313.3 kB

After Optimization

184.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gildedage2.omeka.net main page is 313.3 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. 35% of websites need less resources to load. Javascripts take 225.0 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 10.8 kB

  • Original 16.2 kB
  • After minification 15.1 kB
  • After compression 5.4 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 10.8 kB or 67% of the original size.

Image Optimization

-0%

Potential reduce by 52 B

  • Original 60.6 kB
  • After minification 60.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. Gilded Age 2 Omeka images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 115.0 kB

  • Original 225.0 kB
  • After minification 188.5 kB
  • After compression 110.0 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 115.0 kB or 51% of the original size.

CSS Optimization

-23%

Potential reduce by 2.7 kB

  • Original 11.6 kB
  • After minification 11.3 kB
  • After compression 8.9 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. Gildedage2.omeka.net needs all CSS files to be minified and compressed as it can save up to 2.7 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (67%)

Requests Now

21

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gildedage2.omeka.net

gildedage2.omeka.net

146 ms

js

js

123 ms

public.css

public.css

2 ms

css

css

37 ms

iconfonts.css

iconfonts.css

9 ms

normalize.css

normalize.css

12 ms

style.css

style.css

15 ms

jquery.min.js

jquery.min.js

26 ms

jquery-ui.min.js

jquery-ui.min.js

31 ms

jquery.ui.touch-punch.js

jquery.ui.touch-punch.js

14 ms

selectivizr.js

selectivizr.js

19 ms

jquery-accessibleMegaMenu.js

jquery-accessibleMegaMenu.js

20 ms

respond.js

respond.js

20 ms

jquery-extra-selectors.js

jquery-extra-selectors.js

18 ms

seasons.js

seasons.js

19 ms

globals.js

globals.js

19 ms

print.css

print.css

2 ms

bd0633a1de0aa0c119df80e6df5650cc.jpg

bd0633a1de0aa0c119df80e6df5650cc.jpg

113 ms

2b5fc88389864fd83ad42e7c4fb37013.jpg

2b5fc88389864fd83ad42e7c4fb37013.jpg

128 ms

66caa2f51684c6d0ab370d7336acb368.jpg

66caa2f51684c6d0ab370d7336acb368.jpg

140 ms

ea16742af42d8b87723d2023771fe13e.jpg

ea16742af42d8b87723d2023771fe13e.jpg

149 ms

424b8be62ce84298c77d7be02caeb6d1.jpg

424b8be62ce84298c77d7be02caeb6d1.jpg

136 ms

font

font

92 ms

fa-solid-900.woff

fa-solid-900.woff

19 ms

fa-regular-400.woff

fa-regular-400.woff

18 ms

Accessibility Review

gildedage2.omeka.net accessibility score

98

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.

Best Practices

gildedage2.omeka.net 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

SEO Factors

gildedage2.omeka.net SEO score

100

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

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 Gildedage2.omeka.net 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 Gildedage2.omeka.net 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

gildedage2.omeka.net

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