Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 65% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 100

    SEO

    Google-friendlier than
    96% of websites

read.as

Read.as

Page Load Speed

1.2 sec in total

First Response

453 ms

Resources Loaded

497 ms

Page Rendered

262 ms

read.as screenshot

About Website

Click here to check amazing Read content. Otherwise, check out these important facts you probably never knew about read.as

Long-form reader built on open protocols.

Visit read.as

Key Findings

We analyzed Read.as page load time and found that the first response time was 453 ms and then it took 759 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

read.as performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value2.3 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

read.as

453 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 221 B (37%)

Content Size

597 B

After Optimization

376 B

In fact, the total size of Read.as main page is 597 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 597 B which makes up the majority of the site volume.

HTML Optimization

-37%

Potential reduce by 221 B

  • Original 597 B
  • After minification 588 B
  • After compression 376 B

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 221 B or 37% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

read.as accessibility score

84

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.

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

read.as 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

SEO Factors

read.as 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

    N/A

  • Encoding

    UTF-8

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