5 sec in total
326 ms
3.7 sec
1 sec
Visit reportedly.com now to see the best up-to-date Reportedly content and also check out these interesting facts you probably never knew about reportedly.com
Visit reportedly.comWe analyzed Reportedly.com page load time and found that the first response time was 326 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
reportedly.com performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value3.6 s
62/100
25%
Value2.8 s
96/100
10%
Value0 ms
100/100
30%
Value0.145
77/100
15%
Value3.6 s
92/100
10%
326 ms
490 ms
219 ms
438 ms
134 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Reportedly.com, 24% (27 requests) were made to Prod01-cdn07.cdn.firstlook.org and 19% (22 requests) were made to Prod01-cdn06.cdn.firstlook.org. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source External.xx.fbcdn.net.
Page size can be reduced by 723.8 kB (32%)
2.2 MB
1.5 MB
In fact, the total size of Reportedly.com main page is 2.2 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 228.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. This page needs HTML code to be minified as it can gain 27.9 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 228.9 kB or 87% of the original size.
Potential reduce by 21.7 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. Reportedly images are well optimized though.
Potential reduce by 199.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 199.6 kB or 56% of the original size.
Potential reduce by 273.6 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. Reportedly.com needs all CSS files to be minified and compressed as it can save up to 273.6 kB or 84% of the original size.
Number of requests can be reduced by 44 (41%)
107
63
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reportedly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
reportedly.com
326 ms
reported.ly
490 ms
wp-emoji-release.min.js
219 ms
public.css
438 ms
simple-line-icons.css
134 ms
style.css
435 ms
css
127 ms
style.css
143 ms
colorbox.css
439 ms
timeline-styles.css
150 ms
lightslider.css
449 ms
styles.css
455 ms
css
151 ms
css
163 ms
style.css
154 ms
responsive.css
162 ms
font-awesome.min.css
463 ms
style.css
735 ms
style.css
739 ms
style.css
740 ms
highlight-and-share.css
748 ms
jquery.js
435 ms
jquery-migrate.min.js
424 ms
main.js
435 ms
wp_cat_rss_style.css
767 ms
site.js
144 ms
public.js
329 ms
idle-timer.min.js
334 ms
custom.js
356 ms
imagesloaded.pkgd.min.js
599 ms
owl.carousel.min.js
705 ms
affix.js
384 ms
jquery.matchHeight.js
815 ms
jquery.fitvids.js
816 ms
jquery.sidr.min.js
877 ms
jquery.magnific-popup.min.js
880 ms
custom.js
980 ms
highlight-and-share.js
979 ms
jquery.colorbox-min.js
1021 ms
jquery.newsTicker.min.js
1001 ms
analytics.js
260 ms
GettyImages-516310140-380x260.jpg
1073 ms
AP550569474594-380x260.jpg
1069 ms
Cd59t2DUkAEgDzk.jpg:thumb
323 ms
safe_image.php
1094 ms
12496586_10154642484231002_1028826452_n.jpg
1118 ms
Cd56TRrXEAA5moA.jpg:thumb
272 ms
AP796840950322-380x260.jpg
1368 ms
AP369622329080-380x260.jpg
1369 ms
sb-reportedly-icon.png
1017 ms
favicon.png
1366 ms
5858491007_eeb54359e8_b-375x195.jpg
1420 ms
GettyImages-511703452-375x195.jpg
1597 ms
Stop-Rampal-mangrove-380x260.jpg
1024 ms
AP392357277246-375x195.jpg
1419 ms
12474618_464784887044690_2026269113_n.jpg
1358 ms
12514545_10153572349956939_1989650956_n.jpg
1358 ms
12323492_10154051021645530_808383849_n.jpg
1366 ms
12720032_645001558971474_52312864_n.jpg
1414 ms
12496652_987472464674814_2125881436_n.jpg
1414 ms
10429330_1598256650393898_7698007562452468761_n.png
1413 ms
12323269_922663031149077_313307747_n.jpg
1417 ms
safe_image.php
1097 ms
safe_image.php
1295 ms
safe_image.php
1302 ms
safe_image.php
1417 ms
safe_image.php
1294 ms
safe_image.php
1301 ms
safe_image.php
1590 ms
safe_image.php
1364 ms
safe_image.php
1365 ms
safe_image.php
1413 ms
safe_image.php
1764 ms
safe_image.php
1415 ms
GettyImages-514893442-380x260.jpg
1022 ms
AP392357277246-380x260.jpg
1012 ms
sb-twitter-follow.png
1019 ms
dems-375x195.jpg
1020 ms
AP550569474594-375x195.jpg
1020 ms
logo-normal-beta.png
1011 ms
social-icons.png
1016 ms
share-icons.png
1015 ms
board-icons.png
1018 ms
board-icons-w.png
1010 ms
social-icons-mini.png
1016 ms
GettyImages-514893442-810x613.jpg
1762 ms
GettyImages-516310140-375x195.jpg
1586 ms
AP796840950322-375x195.jpg
1414 ms
AP369622329080-375x195.jpg
1351 ms
jquery.min.js
1088 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
963 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
1163 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
1226 ms
fontawesome-webfont.woff
1448 ms
y7lebkjgREBJK96VQi37ZtIh4imgI8P11RFo6YPCPC0.woff
1277 ms
p.js
1133 ms
collect
790 ms
12779264_1774347789451449_7527381142499103297_o.jpg
348 ms
widgets.css
300 ms
settings
640 ms
reportedly.com
414 ms
12525303_1774113979474830_1840120858245393036_o.jpg
59 ms
12322899_1773546586198236_3150853382637952680_o.jpg
180 ms
12821350_1118217148231232_7278654301927184126_n.jpg
177 ms
11950313_1773000806252814_5101480953768287163_o.jpg
180 ms
12087918_1773544766198418_5239994149157135807_o.jpg
177 ms
12829261_1773088639577364_4378657728351149394_o.jpg
177 ms
10269270_1774057316147163_3792932888735080041_o.jpg
174 ms
12819464_474323689428871_183930986646509884_o.jpg
28 ms
sidebar.js
29 ms
embedded.js
56 ms
ptrack-v0.4.10-engaged-time.js
5 ms
22 ms
reportedly.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
reportedly.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
reportedly.com SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reportedly.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 Reportedly.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.
reportedly.com
Open Graph description is not detected on the main page of Reportedly. 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: