Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

us.readly.com

Readly | All magazines - one magazine app subscription

Page Load Speed

3 sec in total

First Response

13 ms

Resources Loaded

2.2 sec

Page Rendered

794 ms

us.readly.com screenshot

About Website

Visit us.readly.com now to see the best up-to-date Us Readly content for Germany and also check out these interesting facts you probably never knew about us.readly.com

Readly | All your favorite magazines with only one subscription for a fixed price of $11.99 a month. Try the unlimited magazine app for Free!

Visit us.readly.com

Key Findings

We analyzed Us.readly.com page load time and found that the first response time was 13 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

us.readly.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value6,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

us.readly.com

13 ms

us.readly.com

348 ms

1832980389.js

230 ms

application_bootstrap-1caaf308c3d50bd2490267e2566a994d.css

8 ms

application_bootstrap_js-0606023ed1aab316244d009676542b49.js

15 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 17% of them (21 requests) were addressed to the original Us.readly.com, 40% (50 requests) were made to D2g0vx5m9lvvbk.cloudfront.net and 7% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (612 ms) relates to the external source D2g0vx5m9lvvbk.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 923.9 kB (21%)

Content Size

4.4 MB

After Optimization

3.5 MB

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

HTML Optimization

-81%

Potential reduce by 37.2 kB

  • Original 45.8 kB
  • After minification 45.7 kB
  • After compression 8.6 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 37.2 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 13.9 kB

  • Original 3.1 MB
  • After minification 3.1 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. Us Readly images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 504.2 kB

  • Original 793.6 kB
  • After minification 791.2 kB
  • After compression 289.4 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 504.2 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 368.7 kB

  • Original 448.0 kB
  • After minification 446.6 kB
  • After compression 79.3 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. Us.readly.com needs all CSS files to be minified and compressed as it can save up to 368.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (21%)

Requests Now

106

After Optimization

84

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

Accessibility Review

us.readly.com accessibility score

71

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

us.readly.com 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

us.readly.com SEO score

74

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

High

robots.txt is not valid

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

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Us.readly.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 Us.readly.com main page’s claimed encoding is . 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 data is detected on the main page of Us Readly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: