1.5 sec in total
121 ms
899 ms
495 ms
Click here to check amazing Mobile Reuters content for United States. Otherwise, check out these important facts you probably never knew about mobile.reuters.com
Find latest news from every corner of the globe at Reuters.com, your online source for breaking international news coverage.
Visit mobile.reuters.comWe analyzed Mobile.reuters.com page load time and found that the first response time was 121 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
mobile.reuters.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value16.6 s
0/100
25%
Value21.7 s
0/100
10%
Value24,040 ms
0/100
30%
Value0.078
95/100
15%
Value57.1 s
0/100
10%
121 ms
29 ms
41 ms
53 ms
37 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Mobile.reuters.com, 21% (24 requests) were made to S4.reutersmedia.net and 15% (17 requests) were made to S2.reutersmedia.net. The less responsive or slowest element that took the longest time to load (275 ms) relates to the external source Trends.revcontent.com.
Page size can be reduced by 619.2 kB (47%)
1.3 MB
700.3 kB
In fact, the total size of Mobile.reuters.com main page is 1.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. 65% of websites need less resources to load. Javascripts take 687.3 kB which makes up the majority of the site volume.
Potential reduce by 99.9 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 99.9 kB or 79% of the original size.
Potential reduce by 15.1 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. Mobile Reuters images are well optimized though.
Potential reduce by 421.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 421.4 kB or 61% of the original size.
Potential reduce by 82.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. Mobile.reuters.com needs all CSS files to be minified and compressed as it can save up to 82.8 kB or 84% of the original size.
Number of requests can be reduced by 62 (55%)
112
50
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Reuters. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and as a result speed up the page load time.
mobile.reuters.com
121 ms
win-main.css
29 ms
jquery.min.js
41 ms
jquery.cookie.js
53 ms
jquery.idle.min.js
37 ms
jquery-dateFormat.min.js
36 ms
mobile-detect.min.js
50 ms
slick.min.js
48 ms
win-utils.js
47 ms
win-main-header.js
56 ms
win-search.js
34 ms
win-event.js
47 ms
win-trending.js
47 ms
win-wire.js
53 ms
reuters_winnebago_bootstrap.js
5 ms
win-mixpanel.js
31 ms
win-main.js
42 ms
win-sharetools.js
49 ms
gw.js
194 ms
cc_af.js
127 ms
beacon.js
7 ms
gpt.js
8 ms
pubads_impl_81.js
10 ms
container.html
81 ms
mixpanel-2-latest.min.js
106 ms
gtm.js
72 ms
reuters-logo-win-lrg.png
67 ms
win-ico-menu.png
68 ms
search-input-icon.png
65 ms
20160229_9932705720160229200409.jpg
61 ms
ads
91 ms
82 ms
78 ms
76 ms
77 ms
80 ms
76 ms
win-ico-search.png
41 ms
win-menu-open-bg.gif
41 ms
search-input-close.png
40 ms
39 ms
47 ms
47 ms
49 ms
48 ms
79 ms
79 ms
73 ms
win-menu-arrow.png
40 ms
win-ico-wire-arrow.png
41 ms
44 ms
40 ms
75 ms
74 ms
71 ms
45 ms
45 ms
70 ms
70 ms
70 ms
40 ms
36 ms
35 ms
35 ms
39 ms
Knowledge-Regular.woff
73 ms
Knowledge-Medium-webfont.woff
73 ms
p.js
45 ms
17 ms
win-ico-right-arrow.png
11 ms
Knowledge-Light-webfont.woff
10 ms
mobile.reuters.com
9 ms
video-indicator.png
15 ms
ptrack-v0.4.10.js
4 ms
4 ms
slideshow-marker.png
10 ms
serve.js.php
275 ms
win-sprite-follow.png
6 ms
win-ico-picture.png
50 ms
win-ico-video.png
50 ms
analytics.js
45 ms
fbevents.js
39 ms
keywee.min.js
60 ms
breakingNews
131 ms
14 ms
13 ms
9 ms
32 ms
44 ms
45 ms
sp.js
16 ms
gwiq.js
53 ms
176 ms
39 ms
40 ms
873817096.js
120 ms
i
9 ms
189 ms
rev2.min.css
8 ms
rev2.min.js
16 ms
p-aD1qr93XuF6aC.gif
13 ms
img.revcontent.com
19 ms
img.revcontent.com
19 ms
img.revcontent.com
20 ms
img.revcontent.com
18 ms
chartbeat.js
5 ms
rt=ifr
39 ms
ping
28 ms
5907
25 ms
tpc=na_id
17 ms
87e69b15e77198f8020cf8a3e9beb630
40 ms
pixel
19 ms
g.json
42 ms
6 ms
5 ms
362738.gif
10 ms
tpid=-4458213122722499777
5 ms
mobile.reuters.com accessibility score
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
mobile.reuters.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
mobile.reuters.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.reuters.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 Mobile.reuters.com 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.
mobile.reuters.com
Open Graph description is not detected on the main page of Mobile Reuters. 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: