Tools & Wizards About Us
orme.ws screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

orme.ws

Orme Genealogy, Photo Galleries, Web Directory - The Orme web site

Page Load Speed

1.1 sec in total

First Response

223 ms

Resources Loaded

658 ms

Page Rendered

197 ms

orme.ws screenshot

About Website

Visit orme.ws now to see the best up-to-date Orme content and also check out these interesting facts you probably never knew about orme.ws

This site contains Orme genealogy information, the photography of Andrew Orme and a directory of other Orme sites of the web.

Visit orme.ws

Key Findings

We analyzed Orme.ws page load time and found that the first response time was 223 ms and then it took 855 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

orme.ws performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

orme.ws

223 ms

style.css

68 ms

brand

12 ms

show_ads.js

38 ms

brandjs.js

22 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 52% of them (11 requests) were addressed to the original Orme.ws, 14% (3 requests) were made to Pagead2.googlesyndication.com and 10% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (223 ms) belongs to the original domain Orme.ws.

Page Optimization Overview & Recommendations

Page size can be reduced by 27.4 kB (8%)

Content Size

352.7 kB

After Optimization

325.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Orme.ws main page is 352.7 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. 25% of websites need less resources to load. Javascripts take 280.9 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 11.9 kB

  • Original 17.4 kB
  • After minification 16.5 kB
  • After compression 5.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 11.9 kB or 69% of the original size.

Image Optimization

-5%

Potential reduce by 2.3 kB

  • Original 48.1 kB
  • After minification 45.8 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. Orme images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 8.3 kB

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

-77%

Potential reduce by 4.8 kB

  • Original 6.3 kB
  • After minification 4.8 kB
  • After compression 1.5 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. Orme.ws needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (26%)

Requests Now

19

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

orme.ws

orme.ws

223 ms

style.css

style.css

68 ms

brand

brand

12 ms

show_ads.js

show_ads.js

38 ms

brandjs.js

brandjs.js

22 ms

adsbygoogle.js

adsbygoogle.js

74 ms

analytics.js

analytics.js

26 ms

branding.png

branding.png

23 ms

tab_selected.png

tab_selected.png

125 ms

content_header.png

content_header.png

132 ms

link.png

link.png

137 ms

the-great-orme-wales.jpg

the-great-orme-wales.jpg

194 ms

hk-boating-01-s.jpg

hk-boating-01-s.jpg

142 ms

hk-boyfriend-01-s.jpg

hk-boyfriend-01-s.jpg

136 ms

hk-club-house-01-s.jpg

hk-club-house-01-s.jpg

143 ms

bullet.png

bullet.png

218 ms

content_footer.png

content_footer.png

218 ms

collect

collect

59 ms

show_ads_impl.js

show_ads_impl.js

172 ms

zrt_lookup.html

zrt_lookup.html

26 ms

js

js

71 ms

Accessibility Review

orme.ws accessibility score

69

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

[aria-*] attributes do not match their roles

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

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

orme.ws best practices score

83

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

Page has valid source maps

SEO Factors

orme.ws SEO score

77

Search Engine Optimization Advices

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 Orme.ws 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 Orme.ws 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

orme.ws

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