4.5 sec in total
232 ms
4 sec
289 ms
Visit onpublico.com now to see the best up-to-date Onpublico content for Mexico and also check out these interesting facts you probably never knew about onpublico.com
A citizen journalism platform that enables ordinary people to report NEWS. #CitizenJournalism #SocialNews #NewMedia
Visit onpublico.comWe analyzed Onpublico.com page load time and found that the first response time was 232 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
onpublico.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value3.3 s
70/100
25%
Value3.1 s
93/100
10%
Value270 ms
82/100
30%
Value0.099
90/100
15%
Value3.9 s
88/100
10%
232 ms
1705 ms
61 ms
227 ms
79 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 16% of them (13 requests) were addressed to the original Onpublico.com, 22% (18 requests) were made to Vnews.s3.amazonaws.com and 14% (12 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Onpublico.com.
Page size can be reduced by 759.9 kB (50%)
1.5 MB
755.0 kB
In fact, the total size of Onpublico.com main page is 1.5 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. Javascripts take 743.7 kB which makes up the majority of the site volume.
Potential reduce by 88.6 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 33.2 kB, which is 32% 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 88.6 kB or 85% of the original size.
Potential reduce by 26.3 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. Onpublico images are well optimized though.
Potential reduce by 480.3 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 480.3 kB or 65% of the original size.
Potential reduce by 164.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. Onpublico.com needs all CSS files to be minified and compressed as it can save up to 164.7 kB or 83% of the original size.
Number of requests can be reduced by 35 (49%)
71
36
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Onpublico. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
onpublico.com
232 ms
1705 ms
css
61 ms
onpublico.css
227 ms
js
79 ms
sdk.js
432 ms
jquery-2.1.4.min.js
37 ms
angular.min.js
78 ms
vendor.js
702 ms
onpublico.js
374 ms
desktop.js
308 ms
gpt.js
126 ms
analytics.js
126 ms
8d918b852897f7a8c7f916fb41d530c12453950259e195bcf118c92bbbdc6aa0.jpg.620x361_q90_crop-smart_upscale.jpg
865 ms
e3f7fd42603c7160176f78d25129581e44a19f3315c250708eae00d63e6448fd.JPG.29x29_q90_crop-smart_upscale.jpg
833 ms
8a20570defe8c151e5a866839f05499720acb06bdae9605009135ba759b16df5.jpg.620x361_q90_crop-smart_upscale.jpg
969 ms
94554e46db2a49ca4be78f47c02b436853465c93159a195ca44f093e822d77a1.jpg.29x29_q90_crop-smart_upscale.jpg
830 ms
8a20570defe8c151e5a866839f05499720acb06bdae9605009135ba759b16df5.jpg.300x175_q90_crop-smart_upscale.jpg
856 ms
4a03a5dbc1f06c51eeabbc3291b4477971749d1fa14f348171b2035b647fe46e.jpg.300x175_q90_crop-smart_upscale.jpg
855 ms
default.png.29x29_q90_crop-smart_upscale.jpg
855 ms
d10a82c46efd7bcffa5a20ee03b222a7e2b7a6d0c773b8b23370f3a05d07c1a0-00001.png.300x175_q90_crop-smart_upscale.jpg
852 ms
34ae6bb74ae1675b008cb0e2e7d8c8410ad8465b136323e3c32ef5a756b287f8.jpg.29x29_q90_crop-smart_upscale.jpg
980 ms
1e8e1d874d296bac94b0b6aae13e896526ad7d688aaeba4c57e735dc83799690.jpg.300x175_q90_crop-smart_upscale.jpg
980 ms
9e8a3b1947079c9b86b02a239eb8960ddd98682505aa28b19bb4f8d6a3c3f8a2.jpg.300x175_q90_crop-smart_upscale.jpg
1003 ms
71bdb6c726608a2ddc63fe62910329ca018c8769997d6f5d2c725481a5ee35ab.jpg.29x29_q90_crop-smart_upscale.jpg
972 ms
5d5f6adbc3f011859b877207a4cd0584340009d6cfac64975f382c7ab58e8bf4.jpg.300x175_q90_crop-smart_upscale.jpg
1190 ms
2c0d6827f3c8dcfecb1697c17c09f3bd9f43b61fdba1c8b5540fc56b85c604ef.jpg.29x29_q90_crop-smart_upscale.jpg
1192 ms
c7296ec17930934b6246db0c2d64a97b7b1024e959dd7e870461d46a1a5c6de8.jpg.300x175_q90_crop-smart_upscale.jpg
1188 ms
a0fadbec4e32864335c4fba889c4e61bdd9044a8fd231917972fc57f5d87a983.jpg.29x29_q90_crop-smart_upscale.jpg
1189 ms
70a21a7cda7054e63e33bf4d5b825017b62f4e8d891358c265b6be3af76d3176.jpeg.300x175_q90_crop-smart_upscale.jpg
1186 ms
57b74b95781c6e88400736a3beb7305097daa58d087781c713a6f67de5d7ec30.jpeg.81x81_q90_crop-smart_upscale.jpg
1185 ms
onpublico-logol.png
102 ms
__spi.gif
155 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
208 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
208 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
210 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
248 ms
onpublico-icons.woff
205 ms
bg-lreports-title.gif
141 ms
bg-bnews-title.gif
142 ms
pubads_impl_82.js
148 ms
collect
92 ms
collect
111 ms
ads
449 ms
container.html
32 ms
client:plusone.js
375 ms
634 ms
common.js
158 ms
map.js
180 ms
237 ms
formbox-bg.gif
439 ms
xd_arbiter.php
615 ms
StaticMapService.GetMapImage
425 ms
5020041267371466159
106 ms
17073306236540237358
169 ms
osd.js
138 ms
cb=gapi.loaded_0
94 ms
util.js
63 ms
onion.js
67 ms
ViewportInfoService.GetViewportInfo
240 ms
stats.js
50 ms
controls.js
135 ms
postmessageRelay
201 ms
cb=gapi.loaded_1
117 ms
transparent.png
239 ms
css
71 ms
google4.png
203 ms
mapcnt6.png
224 ms
sv5.png
224 ms
vt
34 ms
vt
41 ms
vt
38 ms
vt
32 ms
vt
40 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
20 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
33 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
32 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
33 ms
3193398744-postmessagerelay.js
89 ms
rpc:shindig_random.js
88 ms
xd_arbiter.php
97 ms
AuthenticationService.Authenticate
75 ms
cb=gapi.loaded_0
12 ms
onpublico.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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
onpublico.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
Page has valid source maps
onpublico.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onpublico.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 Onpublico.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.
onpublico.com
Open Graph data is detected on the main page of Onpublico. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: