2.4 sec in total
154 ms
1.6 sec
735 ms
Click here to check amazing Documents content for Mexico. Otherwise, check out these important facts you probably never knew about documents.mx
Share what you know and love through presentations, infographics, documents and more
Visit documents.mxWe analyzed Documents.mx page load time and found that the first response time was 154 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
documents.mx performance score
name
value
score
weighting
Value1.9 s
88/100
10%
Value3.7 s
58/100
25%
Value3.2 s
92/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value3.3 s
94/100
10%
154 ms
165 ms
98 ms
148 ms
111 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 24% of them (21 requests) were addressed to the original Documents.mx, 41% (36 requests) were made to Reader16.documents.mx and 9% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (647 ms) relates to the external source Reader16.documents.mx.
Page size can be reduced by 1.6 MB (42%)
3.8 MB
2.2 MB
In fact, the total size of Documents.mx main page is 3.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 80.0 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 80.0 kB or 88% of the original size.
Potential reduce by 510.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. Obviously, Documents needs image optimization as it can save up to 510.1 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 408.0 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 408.0 kB or 62% of the original size.
Potential reduce by 588.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. Documents.mx needs all CSS files to be minified and compressed as it can save up to 588.6 kB or 86% of the original size.
Number of requests can be reduced by 29 (38%)
76
47
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Documents. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
documents.mx
154 ms
style.css
165 ms
flexslider.css
98 ms
bootstrap.css
148 ms
reader.css
111 ms
animate.min.css
103 ms
magnific-popup.css
97 ms
icon-fonts.css
141 ms
css
271 ms
css
282 ms
css
291 ms
jquery.min.js
107 ms
imgLiquid-min.js
136 ms
plugins.js
197 ms
jquery.themepunch.tools.min.js
209 ms
jquery.themepunch.revolution.min.js
225 ms
isotope.pkgd.min.js
195 ms
functions.js
196 ms
customs.js
205 ms
flexslider-min.js
226 ms
adsbygoogle.js
53 ms
documents.mx_250.png
63 ms
56d36e5e5503461f848b456a_thumb.png
330 ms
56d1f29055034687508b4578_thumb.png
335 ms
56d1f28b5503462c038b4569_thumb.png
331 ms
56d1f286550346e3898b456f_thumb.png
331 ms
56d1f282550346459c8b456e_thumb.png
333 ms
56d1ca655503465d328b4584_thumb.png
329 ms
56d1ca6255034647718b4578_thumb.png
332 ms
56d1ca5f55034643768b457e_thumb.png
332 ms
56d1ca5c550346b6768b4572_thumb.png
335 ms
56d1ca595503465c268b458a_thumb.png
335 ms
56d1ca555503466f2e8b4589_thumb.png
395 ms
56d1ca5155034618638b456c_thumb.png
337 ms
56d1ca4d550346192b8b4581_thumb.png
340 ms
56d1ca4a550346d8768b4571_thumb.png
337 ms
56d1ca47550346192b8b457f_thumb.png
337 ms
56d1ca4455034670708b4576_thumb.png
338 ms
56d1ca40550346e6288b4587_thumb.png
392 ms
56d1c7bc5503463d598b456d_thumb.png
393 ms
56cde39b550346d3578b456c_thumb.png
393 ms
56cc6d97550346508f8b4584_thumb.png
467 ms
56cc6d905503464e928b4568_thumb.png
473 ms
56cc6d8b5503469e8e8b458e_thumb.png
467 ms
56cc6d84550346728f8b4596_thumb.png
469 ms
56c907e7550346ca3e8b456f_thumb.png
469 ms
56c780d9550346cb1d8b456d_thumb.png
624 ms
56c77756550346205f8b4568_thumb.png
467 ms
56c76fc3550346fb738b456b_thumb.png
579 ms
56c75eb3550346a0268b4574_thumb.png
580 ms
56c75b9e550346b2028b456e_thumb.png
623 ms
56c5afca550346d94d8b4568_thumb.png
578 ms
56c5afc755034674448b456a_thumb.png
622 ms
56c5afc3550346553d8b456a_thumb.png
623 ms
56c5afbe550346ee468b456a_thumb.png
623 ms
56c5afba550346f93a8b4568_thumb.png
624 ms
56c5afb7550346824a8b4568_thumb.png
647 ms
56c5afb2550346cd498b4568_thumb.png
647 ms
documents.mx_whilte.png
312 ms
footer_line.png
276 ms
hm-top-arrow.svg
274 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
268 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
269 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
272 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
270 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
270 ms
idealtheme.woff
343 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
269 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
268 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
269 ms
sdk.js
312 ms
154 ms
analytics.js
122 ms
xd_arbiter.php
234 ms
xd_arbiter.php
456 ms
ca-pub-5552168907044179.js
46 ms
zrt_lookup.html
103 ms
show_ads_impl.js
50 ms
collect
20 ms
ads
240 ms
osd.js
14 ms
m_js_controller.js
29 ms
abg.js
51 ms
favicon
62 ms
googlelogo_color_112x36dp.png
60 ms
nessie_icon_tiamat_white.png
38 ms
s
29 ms
x_button_blue2.png
20 ms
documents.mx accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
documents.mx 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
documents.mx 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Documents.mx can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Documents.mx 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.
documents.mx
Open Graph data is detected on the main page of Documents. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: