Report Summary

  • 81

    Performance

    Renders faster than
    86% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

twinotterarchive.com

Twin Otter Current

Page Load Speed

23.4 sec in total

First Response

193 ms

Resources Loaded

20.9 sec

Page Rendered

2.3 sec

twinotterarchive.com screenshot

About Website

Welcome to twinotterarchive.com homepage info - get ready to check Twin Otter Archive best content right away, or after learning these important things about twinotterarchive.com

Dedicated to the de Havilland Canada DHC-6 Twin Otter by Neil Aird, from original data by the late Michael J. Ody, assisted over the years by Ian Macintosh.

Visit twinotterarchive.com

Key Findings

We analyzed Twinotterarchive.com page load time and found that the first response time was 193 ms and then it took 23.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

twinotterarchive.com performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

twinotterarchive.com

193 ms

twinotterarchive.com

403 ms

background.css

183 ms

0300e0e0_green_stroke.png

196 ms

Count.cgi

461 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 72% of them (26 requests) were addressed to the original Twinotterarchive.com, 19% (7 requests) were made to Rf.revolvermaps.com and 6% (2 requests) were made to Paypalobjects.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Web.archive.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 101.7 kB (4%)

Content Size

2.8 MB

After Optimization

2.7 MB

In fact, the total size of Twinotterarchive.com main page is 2.8 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. 30% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 46.5 kB

  • Original 55.2 kB
  • After minification 50.9 kB
  • After compression 8.7 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 46.5 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 55.1 kB

  • Original 2.7 MB
  • After minification 2.6 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. Twin Otter Archive images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 7 B

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

-33%

Potential reduce by 36 B

  • Original 110 B
  • After minification 99 B
  • After compression 74 B

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. Twinotterarchive.com needs all CSS files to be minified and compressed as it can save up to 36 B or 33% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

32

After Optimization

32

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

Accessibility Review

twinotterarchive.com accessibility score

52

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

Best Practices

twinotterarchive.com 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

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

twinotterarchive.com SEO score

62

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Twinotterarchive.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 Twinotterarchive.com 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

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