Tools & Wizards About Us

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

historicaltextarchive.org

Historical Text Archive: Electronic History Resources, online since 1990

Page Load Speed

712 ms in total

First Response

232 ms

Resources Loaded

280 ms

Page Rendered

200 ms

About Website

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

Now in its 26th year, the Historical Text Archive publishes high quality articles, books, essays, documents, historical photos, and links, screened for content, for a broad range of historical subject...

Visit historicaltextarchive.org

Key Findings

We analyzed Historicaltextarchive.org page load time and found that the first response time was 232 ms and then it took 480 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

historicaltextarchive.org performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value1.1 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

historicaltextarchive.org

232 ms

fckeditor.js

4 ms

prototype.js.pagespeed.jm.KlhP454wI7.js

7 ms

bg2.gif.pagespeed.ce.Kk_Cfbo9UM.gif

28 ms

hta2_0.jpg.pagespeed.ce.wN0cArQWVz.jpg

28 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 14.3 kB (24%)

Content Size

60.2 kB

After Optimization

45.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Historicaltextarchive.org main page is 60.2 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. 15% of websites need less resources to load. HTML takes 26.3 kB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 14.3 kB

  • Original 26.3 kB
  • After minification 24.7 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 14.3 kB or 54% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 15.9 kB
  • After minification 15.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. Historical Text Archive images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 18.0 kB
  • After minification 18.0 kB
  • After compression 18.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. This website has mostly compressed JavaScripts.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

  • Images
  • JavaScript

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

Network Requests Diagram

Accessibility Review

historicaltextarchive.org accessibility score

60

Accessibility Issues

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

historicaltextarchive.org best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

historicaltextarchive.org SEO score

69

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Historicaltextarchive.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 Historicaltextarchive.org main page’s claimed encoding is iso-8859-1. 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 Historical Text Archive. 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: