Tools & Wizards About Us
a11ymetadata.org screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

a11ymetadata.org

Accessibility Metadata Project | Making Accessible Content Discoverable: A Benetech Led Proposal for Accessibility Metadata in Schema.org

Page Load Speed

2.2 sec in total

First Response

228 ms

Resources Loaded

1.4 sec

Page Rendered

618 ms

a11ymetadata.org screenshot

About Website

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

Accessibility Metadata Project looks to define accessibility metadata for use in Schema.org and other mechanisms, such as the Learning Registry

Visit a11ymetadata.org

Key Findings

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

Performance Metrics

a11ymetadata.org performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value1,390 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

www.a11ymetadata.org

228 ms

ga.js

8 ms

flick.css

188 ms

www.a11ymetadata.org

189 ms

otw-grid.css

186 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 78% of them (35 requests) were addressed to the original A11ymetadata.org, 9% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (602 ms) belongs to the original domain A11ymetadata.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 94.7 kB (29%)

Content Size

323.7 kB

After Optimization

229.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of A11ymetadata.org main page is 323.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. 40% of websites need less resources to load. Javascripts take 148.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 69.8 kB

  • Original 90.6 kB
  • After minification 88.3 kB
  • After compression 20.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 69.8 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 334 B

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

JavaScript Optimization

-13%

Potential reduce by 18.8 kB

  • Original 148.5 kB
  • After minification 148.5 kB
  • After compression 129.8 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 18.8 kB or 13% of the original size.

CSS Optimization

-16%

Potential reduce by 5.8 kB

  • Original 36.6 kB
  • After minification 36.6 kB
  • After compression 30.8 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. A11ymetadata.org needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (79%)

Requests Now

39

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.a11ymetadata.org

www.a11ymetadata.org

228 ms

ga.js

ga.js

8 ms

flick.css

flick.css

188 ms

www.a11ymetadata.org

www.a11ymetadata.org

189 ms

otw-grid.css

otw-grid.css

186 ms

general_foundicons.css

general_foundicons.css

179 ms

social_foundicons.css

social_foundicons.css

158 ms

otw_shortcode.css

otw_shortcode.css

208 ms

style.min.css

style.min.css

317 ms

application.css

application.css

296 ms

css

css

20 ms

style.css

style.css

251 ms

jquery.min.js

jquery.min.js

415 ms

jquery-migrate.min.js

jquery-migrate.min.js

338 ms

scrollTo.js

scrollTo.js

336 ms

jquery.form.min.js

jquery.form.min.js

337 ms

mailchimp.js

mailchimp.js

380 ms

core.min.js

core.min.js

447 ms

datepicker.js

datepicker.js

485 ms

knockout-2.2.1.js

knockout-2.2.1.js

459 ms

hexmd5.js

hexmd5.js

430 ms

application.js

application.js

474 ms

spin.min.js

spin.min.js

482 ms

Placeholders.js

Placeholders.js

499 ms

jquery.nicescroll.js

jquery.nicescroll.js

560 ms

__utm.gif

__utm.gif

12 ms

lyte-min.js

lyte-min.js

547 ms

shCore.js

shCore.js

557 ms

shBrushXml.js

shBrushXml.js

589 ms

accessible-dropdown-menus.js

accessible-dropdown-menus.js

589 ms

current-menu-item.js

current-menu-item.js

546 ms

navigation.js

navigation.js

602 ms

style.css

style.css

441 ms

88x31.png

88x31.png

66 ms

Accessibility-Information-300x200.png

Accessibility-Information-300x200.png

111 ms

Feature-Filters.png

Feature-Filters.png

121 ms

88x31.png

88x31.png

63 ms

shCore.css

shCore.css

88 ms

shThemeDefault.css

shThemeDefault.css

83 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

6 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

10 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

13 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

15 ms

0.jpg

0.jpg

22 ms

lytesprite.png

lytesprite.png

76 ms

Accessibility Review

a11ymetadata.org accessibility score

94

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

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

a11ymetadata.org best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

a11ymetadata.org SEO score

87

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 A11ymetadata.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 A11ymetadata.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

a11ymetadata.org

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