3.6 sec in total
180 ms
2.8 sec
525 ms
Click here to check amazing Readly content for Germany. Otherwise, check out these important facts you probably never knew about readly.com
Readly is the new way to read magazines. All your favorites, as much and as often as you like for a fixed price of $9.99 per month. Try us for Free!
Visit readly.comWe analyzed Readly.com page load time and found that the first response time was 180 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
readly.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value5.8 s
15/100
25%
Value5.5 s
55/100
10%
Value360 ms
72/100
30%
Value0.011
100/100
15%
Value7.8 s
45/100
10%
180 ms
414 ms
63 ms
281 ms
538 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Readly.com, 38% (50 requests) were made to D2g0vx5m9lvvbk.cloudfront.net and 16% (21 requests) were made to Us.readly.com. The less responsive or slowest element that took the longest time to load (720 ms) relates to the external source D3ry4o1su9a59w.cloudfront.net.
Page size can be reduced by 869.3 kB (20%)
4.3 MB
3.5 MB
In fact, the total size of Readly.com main page is 4.3 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.
Potential reduce by 37.2 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.
Potential reduce by 13.9 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. Readly images are well optimized though.
Potential reduce by 448.5 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 448.5 kB or 61% of the original size.
Potential reduce by 369.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. Readly.com needs all CSS files to be minified and compressed as it can save up to 369.8 kB or 82% of the original size.
Number of requests can be reduced by 21 (20%)
105
84
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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.
readly.com
180 ms
readly.com
414 ms
en
63 ms
us.readly.com
281 ms
1832980389.js
538 ms
application_bootstrap-e944476e1ce545dfa2cba7d1f9637653.css
6 ms
application_bootstrap_js-192c2244486376ce740da6d58ad21411.js
10 ms
css
57 ms
Readly_logo_grey-85f450da1a08be9674ead8cb9cb77611.svg
15 ms
visamastercard_new-93dd40a65d1c87d88ad2db5ad5270ba8.png
189 ms
paypal-a5369bd37d8b5f2cd388c9a4105daeb6.png
151 ms
enjoyreadly_white_bgr-82f597adcc2d480c124438549071ee9b.svg
186 ms
convenient-9c3e9e3d28a9ccaacb7736129791d203.svg
191 ms
discovernewtitles-f553286a86205f32849e150129d5436f.svg
208 ms
us-0cbe3785551c608a341405a4faff7141.jpg
247 ms
enjoyreadly_mobileversion-6095b4e9d0083ee5c412449a6b6c4c7e.svg
192 ms
all.js
251 ms
flags_new-b3b0aff4d199294b19c449a36086b1bb.png
317 ms
global-84baaf55e5c0466ffd893e49f29c8506.jpg
198 ms
container-arrow-1a0a4a62d9a327e590dd7e05b0adcc3f.svg
211 ms
ipad-a23cf26e855757e026a4f532478cfa42.svg
203 ms
list-check-9ada0c17876ac6f595451b1bca140e52.svg
225 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
302 ms
vzIUHo9z-oJ4WgkpPOtg1_esZW2xOQ-xsNqO47m55DA.woff
232 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
234 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
298 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
299 ms
2EBeVssYDlg
276 ms
7m8l7TlFO-S3VkhHuR0at4bN6UDyHWBl620a-IRfuBk.woff
263 ms
12mE4jfMSBTmg-81EiS-YRsxEYwM7FgeyaSgU71cLG0.woff
264 ms
1pO9eUAp8pSF8VnRTP3xnvesZW2xOQ-xsNqO47m55DA.woff
271 ms
OLffGBTaF0XFOW1gnuHF0YbN6UDyHWBl620a-IRfuBk.woff
275 ms
gtm.js
281 ms
country_continents
174 ms
us-5f76f33e10419733046a03d08e774473.jpg
237 ms
global-01a3666c0475144c6f5fcd7c758fcaa0.jpg
248 ms
global-6cc5a65deb83fb5bc4aaff304d339400.jpg
268 ms
320-0001.jpg
292 ms
320-0001.jpg
310 ms
320-0001.jpg
229 ms
320-0001.jpg
337 ms
320-0001.jpg
283 ms
155 ms
320-0001.jpg
199 ms
320-0001.jpg
318 ms
www-embed-player-vflQrT_sR.css
156 ms
www-embed-player.js
246 ms
base.js
367 ms
xd_arbiter.php
149 ms
320-0001.jpg
290 ms
320-0001.jpg
310 ms
320-0001.jpg
309 ms
320-0001.jpg
310 ms
160-0001.jpg
431 ms
216-0001.jpg
289 ms
432-0001.jpg
446 ms
216-0001.jpg
430 ms
analytics.js
156 ms
conversion_async.js
241 ms
ebOneTag.js
203 ms
160-0001.jpg
396 ms
activityi;src=4480473;type=Count0;cat=Readl0;ord=9957616292848;~oref=https%3A%2F%2Fus.readly.com%2F
229 ms
activityi;src=4480473;type=Count0;cat=Globa0;ord=3436361646117;~oref=https%3A%2F%2Fus.readly.com%2F
231 ms
activityi;src=4480473;type=Count0;cat=Globa00;ord=2928095588437;~oref=https%3A%2F%2Fus.readly.com%2F
246 ms
160-0001.jpg
382 ms
432-0001.jpg
416 ms
320-0001.jpg
408 ms
160-0001.jpg
427 ms
320-0001.jpg
459 ms
320-0001.jpg
720 ms
320-0001.jpg
499 ms
320-0001.jpg
391 ms
320-0001.jpg
248 ms
320-0001.jpg
424 ms
320-0001.jpg
682 ms
320-0001.jpg
407 ms
320-0001.jpg
440 ms
160-0001.jpg
448 ms
432-0001.jpg
515 ms
160-0001.jpg
466 ms
216-0001.jpg
595 ms
160-0001.jpg
427 ms
216-0001.jpg
518 ms
collect
86 ms
collect
251 ms
432-0001.jpg
390 ms
160-0001.jpg
427 ms
Serving
273 ms
fbds.js
43 ms
320-0001.jpg
510 ms
cirt_v1.min.js
194 ms
200 ms
320-0001.jpg
380 ms
320-0001.jpg
373 ms
320-0001.jpg
372 ms
320-0001.jpg
461 ms
320-0001.jpg
375 ms
120 ms
320-0001.jpg
447 ms
320-0001.jpg
454 ms
216-0001.jpg
425 ms
216-0001.jpg
394 ms
160-0001.jpg
500 ms
432-0001.jpg
538 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
64 ms
ad_status.js
71 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
34 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
33 ms
160-0001.jpg
371 ms
320-0001.jpg
334 ms
160-0001.jpg
418 ms
320-0001.jpg
38 ms
320-0001.jpg
428 ms
432-0001.jpg
400 ms
78 ms
cp
77 ms
pixel
53 ms
pixel
55 ms
49 ms
generic
53 ms
generic
49 ms
activityi;src=4383165;type=invmedia;cat=kdvpjvbf;ord=3194952700287.1035
112 ms
conv
70 ms
pixel
56 ms
pixel
58 ms
7 ms
5 ms
generic
5 ms
generic
4 ms
generic
9 ms
generic
9 ms
readly.com accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
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
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
<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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
readly.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
readly.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Readly.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 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.
readly.com
Open Graph data is detected on the main page of Readly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: