3 sec in total
13 ms
2.2 sec
794 ms
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.comWe 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.
us.readly.com performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value7.4 s
4/100
25%
Value6.9 s
34/100
10%
Value6,550 ms
0/100
30%
Value0.012
100/100
15%
Value12.3 s
15/100
10%
13 ms
348 ms
230 ms
8 ms
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 size can be reduced by 923.9 kB (21%)
4.4 MB
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.
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. Us Readly images are well optimized though.
Potential reduce by 504.2 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.
Potential reduce by 368.7 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.
Number of requests can be reduced by 22 (21%)
106
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.
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
css
60 ms
Readly_logo_grey-3898b8d3a6af553d7985163390153d2d.svg
22 ms
visamastercard_new-668e17b0f664669eba27d40bd19c0c73.png
226 ms
paypal-d4a3aa4820e022f3de2692c57931fb2a.png
218 ms
enjoyreadly_white_bgr-d452ceaac7fd125561c425ebb46fbc38.svg
227 ms
convenient-0ae5c0086cc08a76944cf24a26226361.svg
273 ms
discovernewtitles-78f18819a0658a1784783e4e2b8d0110.svg
278 ms
us-8b013cdd2a45956f366e50ff975b05c3.jpg
381 ms
enjoyreadly_mobileversion-b5c9e472c40aa23104fcaad2b792cebb.svg
266 ms
all.js
294 ms
flags_new-b3e535af3079adc072e5c314deba8a32.png
418 ms
global-ac327de97e278fdc91e374bb2cc5cec4.jpg
261 ms
container-arrow-5c986c26049eb65c1b00c0c2251b1696.svg
352 ms
ipad-791b827a83709b67ac4dfefb4a59a83f.svg
354 ms
list-check-2b35aebbc2f87ff308ac83c1de67bf05.svg
352 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
271 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
415 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
415 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
395 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
398 ms
2EBeVssYDlg
423 ms
7m8l7TlFO-S3VkhHuR0at50EAVxt0G0biEntp43Qt6E.ttf
346 ms
12mE4jfMSBTmg-81EiS-YS3USBnSvpkopQaUR-2r7iU.ttf
355 ms
W4wDsBUluyw0tK3tykhXEfesZW2xOQ-xsNqO47m55DA.ttf
390 ms
OLffGBTaF0XFOW1gnuHF0Z0EAVxt0G0biEntp43Qt6E.ttf
390 ms
gtm.js
396 ms
country_continents
242 ms
us-7fad609ec2c5733a2d8c50a22bdb7329.jpg
346 ms
global-396baab8fca8454cf490d6c8fe6e2d01.jpg
365 ms
global-c902af5061b1393bdfa06e597a013c56.jpg
403 ms
320-0001.jpg
288 ms
320-0001.jpg
410 ms
320-0001.jpg
273 ms
320-0001.jpg
325 ms
320-0001.jpg
349 ms
320-0001.jpg
348 ms
250 ms
320-0001.jpg
241 ms
xd_arbiter.php
217 ms
320-0001.jpg
224 ms
320-0001.jpg
260 ms
320-0001.jpg
256 ms
432-0001.jpg
350 ms
320-0001.jpg
320 ms
160-0001.jpg
294 ms
www-embed-player-vflfNyN_r.css
178 ms
www-embed-player.js
246 ms
base.js
328 ms
160-0001.jpg
264 ms
216-0001.jpg
291 ms
160-0001.jpg
292 ms
216-0001.jpg
295 ms
160-0001.jpg
294 ms
analytics.js
160 ms
conversion_async.js
197 ms
ebOneTag.js
132 ms
432-0001.jpg
414 ms
activityi;src=4480473;type=Count0;cat=Readl0;ord=9645211305050;~oref=https%3A%2F%2Fus.readly.com%2F
185 ms
activityi;src=4480473;type=Count0;cat=Globa0;ord=2656689638761;~oref=https%3A%2F%2Fus.readly.com%2F
189 ms
activityi;src=4480473;type=Count0;cat=Globa00;ord=9157350704190;~oref=https%3A%2F%2Fus.readly.com%2F
183 ms
320-0001.jpg
246 ms
320-0001.jpg
396 ms
320-0001.jpg
258 ms
320-0001.jpg
584 ms
320-0001.jpg
235 ms
320-0001.jpg
261 ms
160-0001.jpg
344 ms
320-0001.jpg
343 ms
320-0001.jpg
362 ms
320-0001.jpg
331 ms
432-0001.jpg
548 ms
320-0001.jpg
365 ms
160-0001.jpg
376 ms
216-0001.jpg
295 ms
160-0001.jpg
324 ms
160-0001.jpg
419 ms
216-0001.jpg
420 ms
432-0001.jpg
343 ms
Serving
351 ms
fbds.js
90 ms
320-0001.jpg
408 ms
collect
91 ms
collect
272 ms
cirt_v1.min.js
263 ms
320-0001.jpg
345 ms
320-0001.jpg
367 ms
320-0001.jpg
414 ms
320-0001.jpg
408 ms
320-0001.jpg
362 ms
243 ms
320-0001.jpg
351 ms
48 ms
216-0001.jpg
410 ms
320-0001.jpg
347 ms
432-0001.jpg
476 ms
216-0001.jpg
431 ms
160-0001.jpg
612 ms
160-0001.jpg
412 ms
320-0001.jpg
386 ms
160-0001.jpg
450 ms
432-0001.jpg
530 ms
320-0001.jpg
397 ms
320-0001.jpg
134 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
74 ms
ad_status.js
56 ms
cp
194 ms
pixel
31 ms
pixel
37 ms
86 ms
83 ms
generic
69 ms
activityi;src=4383165;type=invmedia;cat=kdvpjvbf;ord=7257429598830.641
129 ms
generic
23 ms
pixel
61 ms
pixel
57 ms
5 ms
4 ms
conv
50 ms
match
4 ms
generic
17 ms
generic
5 ms
us.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.
us.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
us.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
EN
N/A
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.
us.readly.com
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: