Tools & Wizards About Us
pl.readly.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

pl.readly.com

Readly | All magazines - one magazine app subscription

Page Load Speed

2.8 sec in total

First Response

168 ms

Resources Loaded

1.9 sec

Page Rendered

718 ms

pl.readly.com screenshot

About Website

Welcome to pl.readly.com homepage info - get ready to check Pl Readly best content for Germany right away, or after learning these important things about pl.readly.com

Readly | All your favourite magazines with only one subscription for a fixed price of €14.99 a month. Try the unlimited magazine app for Free!

Visit pl.readly.com

Key Findings

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

Performance Metrics

pl.readly.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value1,700 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

pl.readly.com

168 ms

pl.readly.com

655 ms

gtm.js

567 ms

runtime-d236d4fb50c1639ede4e.js

69 ms

8196-9fd2db0bb01f8128cd9e.js

208 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 36% of them (15 requests) were addressed to the original Pl.readly.com, 26% (11 requests) were made to Dnjpbxg2wcpr8.cloudfront.net and 14% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (655 ms) belongs to the original domain Pl.readly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 205.7 kB (27%)

Content Size

772.8 kB

After Optimization

567.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pl.readly.com main page is 772.8 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. 50% of websites need less resources to load. Javascripts take 297.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 196.9 kB

  • Original 241.2 kB
  • After minification 220.4 kB
  • After compression 44.3 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 196.9 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 8.8 kB

  • Original 165.8 kB
  • After minification 157.0 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. Pl Readly images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 37 B

  • Original 297.6 kB
  • After minification 297.6 kB
  • After compression 297.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

-0%

Potential reduce by 23 B

  • Original 68.1 kB
  • After minification 68.1 kB
  • After compression 68.1 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. Pl.readly.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (38%)

Requests Now

29

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pl 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 12 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

pl.readly.com

pl.readly.com

168 ms

pl.readly.com

pl.readly.com

655 ms

gtm.js

gtm.js

567 ms

runtime-d236d4fb50c1639ede4e.js

runtime-d236d4fb50c1639ede4e.js

69 ms

8196-9fd2db0bb01f8128cd9e.js

8196-9fd2db0bb01f8128cd9e.js

208 ms

6177-129e61355deb6391957a.js

6177-129e61355deb6391957a.js

275 ms

6486-6cde9ccbbbf3db1e9f78.js

6486-6cde9ccbbbf3db1e9f78.js

277 ms

3823-1ba688dd364df50dd517.js

3823-1ba688dd364df50dd517.js

282 ms

4699-796c202be814ab7a4033.js

4699-796c202be814ab7a4033.js

343 ms

4996-0840686ed9a1b8041280.js

4996-0840686ed9a1b8041280.js

219 ms

2496-8cb2a8ac7250e8d8d50c.js

2496-8cb2a8ac7250e8d8d50c.js

286 ms

9861-ddf4242020d2d95c3ac8.js

9861-ddf4242020d2d95c3ac8.js

284 ms

application-1d1a8bf0e76f6f4e31e4.js

application-1d1a8bf0e76f6f4e31e4.js

353 ms

home-0d2904445a6a5714a1142dfe27b25f0c1022de0aeeaccbe6e3e72b284f4a2b06.js

home-0d2904445a6a5714a1142dfe27b25f0c1022de0aeeaccbe6e3e72b284f4a2b06.js

505 ms

application-6062fc7905df1437127bde1d8134105bff7aedb36604d8d4fedbc800c3280b64.css

application-6062fc7905df1437127bde1d8134105bff7aedb36604d8d4fedbc800c3280b64.css

469 ms

readly_logo_light.svg

readly_logo_light.svg

151 ms

uploads%2Fglobal_assets%2Fn30ad4twk3-US_mobile-article_274x546px.png

uploads%2Fglobal_assets%2Fn30ad4twk3-US_mobile-article_274x546px.png

152 ms

AppStore-Readly-Denim.svg

AppStore-Readly-Denim.svg

579 ms

Play-Readly-Denim.svg

Play-Readly-Denim.svg

577 ms

b3NrZG1rO0BKL3p-bmFnbHFle3x6XHJkJSwpf34rLHkVRUNCQkEWRh8aGBscHR5MURQAcAEDAw8LWFkOWARbB3RxJCFyIHZ3eHkrKGl_DXpkMmBiNzNlMzk4PD9sOTw8AVFSU1RVU0JaKl9dWVVdCkYTFkoRTUJHQEtCTkxNTk-55Kexx7C1tbG-urm7vb-4oKX2o_f0oaeoqaqv_bis3JWXl5uQlZGVzJDPk5idlpmBhYKDhIXVj57L38jT0cvLqa6s_vD29OG8rKe7oKy6qu2lt76kubejvYa-vqq0vbq_kZCMu9fW1dq22Y_KmZeflcyemoeB

b3NrZG1rO0BKL3p-bmFnbHFle3x6XHJkJSwpf34rLHkVRUNCQkEWRh8aGBscHR5MURQAcAEDAw8LWFkOWARbB3RxJCFyIHZ3eHkrKGl_DXpkMmBiNzNlMzk4PD9sOTw8AVFSU1RVU0JaKl9dWVVdCkYTFkoRTUJHQEtCTkxNTk-55Kexx7C1tbG-urm7vb-4oKX2o_f0oaeoqaqv_bis3JWXl5uQlZGVzJDPk5idlpmBhYKDhIXVj57L38jT0cvLqa6s_vD29OG8rKe7oKy6qu2lt76kubejvYa-vqq0vbq_kZCMu9fW1dq22Y_KmZeflcyemoeB

156 ms

readly_logo_light_silhouette.svg

readly_logo_light_silhouette.svg

151 ms

pl.png

pl.png

147 ms

uploads%2Fglobal_assets%2F45yppi3cfuc-whitearrow.svg

uploads%2Fglobal_assets%2F45yppi3cfuc-whitearrow.svg

600 ms

list-check-small.svg

list-check-small.svg

616 ms

star_fill.svg

star_fill.svg

57 ms

css2

css2

150 ms

css2

css2

150 ms

arrow_bold.svg

arrow_bold.svg

17 ms

uploads%2Fglobal_assets%2Fmoikvjhfdi-background-shapes_desktop.svg

uploads%2Fglobal_assets%2Fmoikvjhfdi-background-shapes_desktop.svg

398 ms

huaweiappgallery.png

huaweiappgallery.png

165 ms

432-0001.jpg

432-0001.jpg

121 ms

roboto-v18-latin-regular.woff

roboto-v18-latin-regular.woff

25 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

116 ms

roboto-v18-latin-500.woff

roboto-v18-latin-500.woff

25 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

148 ms

roboto-v18-latin-700.woff

roboto-v18-latin-700.woff

25 ms

0QI6MX1D_JOuGQbT0gvTJPa787z5vCJG.ttf

0QI6MX1D_JOuGQbT0gvTJPa787z5vCJG.ttf

188 ms

0QI6MX1D_JOuGQbT0gvTJPa787zAvCJG.ttf

0QI6MX1D_JOuGQbT0gvTJPa787zAvCJG.ttf

197 ms

0QI6MX1D_JOuGQbT0gvTJPa787wsuyJG.ttf

0QI6MX1D_JOuGQbT0gvTJPa787wsuyJG.ttf

196 ms

0QI6MX1D_JOuGQbT0gvTJPa787weuyJG.ttf

0QI6MX1D_JOuGQbT0gvTJPa787weuyJG.ttf

196 ms

slick-f49f279637e425f10e4bbc8f0aed858fa54117ad5a41f477ff1159db93a61114.woff

slick-f49f279637e425f10e4bbc8f0aed858fa54117ad5a41f477ff1159db93a61114.woff

102 ms

fa-brands-400.woff

fa-brands-400.woff

69 ms

Accessibility Review

pl.readly.com accessibility score

85

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

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

pl.readly.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

pl.readly.com SEO score

82

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

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

    EN

  • Encoding

    N/A

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

pl.readly.com

Open Graph data is detected on the main page of Pl Readly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: