2.8 sec in total
194 ms
2.3 sec
223 ms
Welcome to mogitoldos.com.br homepage info - get ready to check Mogi Toldos best content right away, or after learning these important things about mogitoldos.com.br
fábrica de toldo
Visit mogitoldos.com.brWe analyzed Mogitoldos.com.br page load time and found that the first response time was 194 ms and then it took 2.6 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.
mogitoldos.com.br performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value8.5 s
1/100
25%
Value7.4 s
27/100
10%
Value820 ms
35/100
30%
Value0.028
100/100
15%
Value13.0 s
12/100
10%
194 ms
166 ms
103 ms
43 ms
60 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Mogitoldos.com.br, 38% (40 requests) were made to Static.parastorage.com and 19% (20 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (778 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.5 MB (52%)
4.9 MB
2.3 MB
In fact, the total size of Mogitoldos.com.br main page is 4.9 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. 75% 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. Javascripts take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 69.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 69.0 kB or 83% of the original size.
Potential reduce by 56.8 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. Mogi Toldos images are well optimized though.
Potential reduce by 2.1 MB
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 2.1 MB or 75% of the original size.
Potential reduce by 255.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. Mogitoldos.com.br needs all CSS files to be minified and compressed as it can save up to 255.6 kB or 83% of the original size.
Number of requests can be reduced by 67 (71%)
94
27
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mogi Toldos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
mogitoldos.com.br
194 ms
www.mogitoldos.com.br
166 ms
bt
103 ms
require.min.js
43 ms
main-r.min.js
60 ms
viewer.css
60 ms
dynamicmodel
7 ms
6e3f99_179b670342692260507a4c6522b5693d_153.json.z
332 ms
6e3f99_84b51facd5e950aea08ce8db6e05b31b_153.json.z
335 ms
ugc-viewer
100 ms
bt
104 ms
skins.min.js
92 ms
components.min.js
103 ms
utils.min.js
88 ms
core.min.js
89 ms
react-with-addons.min.js
46 ms
lodash.min.js
317 ms
TweenMax.min.js
90 ms
layout.min.js
315 ms
tpa.min.js
88 ms
fonts.min.js
88 ms
animations.min.js
91 ms
swfobject.min.js
90 ms
mousetrap.min.js
91 ms
tweenEngine.min.js
91 ms
DrawSVGPlugin.min.js
91 ms
react-dom.min.js
90 ms
ScrollToPlugin.min.js
92 ms
widgets.min.js
92 ms
experiment.js
94 ms
render.min.js
94 ms
wixappsCore.min.js
312 ms
wixappsBuilder.min.js
311 ms
zepto.min.js
93 ms
color.min.js
308 ms
react-dom-server.min.js
156 ms
bt
94 ms
latin.css
20 ms
dc.js
374 ms
bt
369 ms
6e3f99_e4fc2cab81e44896a5abc34273041e98.png
229 ms
liftedshadow_medium.png
170 ms
css
168 ms
6e3f99_3f9161912e30ad7616be5ad965f08a59.html
248 ms
Slicebox.html
176 ms
6e3f99_f663a2783bb24783a73713595aa14aa5.jpg
331 ms
6e3f99_348a766b9406458499af1b75f8381db6.png
335 ms
6e3f99_03a635feaba14b4f87d4ddc757c8f800.png
440 ms
6e3f99_563d27e42aa84d559de59248b1dfaefa.png
336 ms
6e3f99_7726daabdccf47b1a78704c4aa6bb859.png
435 ms
6e3f99_932bf8f2afc143aeae532fc47ddb47d3.png
328 ms
6e3f99_64a8c9c42c55411fb5b437162f460b39.png
573 ms
6e3f99_23fb63fcd63a4eb085fcf717e90764b9.png
492 ms
6e3f99_4ef3fcb5c608489c913a5a3bb5ef84f3.png
547 ms
6e3f99_bec5f5a491624d9aa378f79b9165ccba.png
668 ms
6e3f99_96a936f7021c42368fd1b5ab658024e5.png
666 ms
6e3f99_9935cc2a6df54fca8406853e37d8b58c.png
778 ms
6e3f99_3c702075ac0e46bea5af7e6be98d5160.png
678 ms
6e3f99_5a8cb073a46849468d655a31765c94af.png
746 ms
bt
209 ms
bt
208 ms
bt
181 ms
O7xuRZhi4u0
285 ms
slicebox.css
159 ms
modernizr.custom.46884.js
159 ms
Wix.js
195 ms
jquery.min.js
250 ms
jquery.hammer-1.0.5.min.js
157 ms
jquery.slicebox.js
157 ms
opensans-bold-webfont.woff
136 ms
opensans-regular-webfont.woff
169 ms
234c98b8-36ae-45ab-8a55-77980708b2bc.woff
164 ms
-KTKVm0Mx9ZCRXL9CXVIbaCWcynf_cDxXwCLxiixG1c.ttf
97 ms
I27Pb-wEGH2ajLYP0QrtSInF5uFdDttMLvmWuJdhhgs.ttf
125 ms
img-bxDcyb9Z-56.gif
450 ms
ad.js
451 ms
ga-audiences
232 ms
shadow.png
81 ms
ga.js
118 ms
www-embed-player-vflfNyN_r.css
166 ms
www-embed-player.js
201 ms
ugc-viewer
130 ms
6e3f99_92973ee350714978b55d0e8d4b350c93.png
537 ms
6e3f99_a690537c82524516874d536ff9e66e0e.png
543 ms
__utm.gif
88 ms
__utm.gif
35 ms
__utm.gif
39 ms
__utm.gif
37 ms
__utm.gif
37 ms
__utm.gif
62 ms
__utm.gif
37 ms
__utm.gif
38 ms
__utm.gif
63 ms
__utm.gif
62 ms
__utm.gif
62 ms
6e3f99_c7a38f601e544ff898fce25a463ebb58.jpg
426 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
35 ms
ad_status.js
57 ms
ga.js
53 ms
js15_as.js
29 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
86 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
82 ms
0.php
68 ms
__utm.gif
54 ms
mogitoldos.com.br 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
mogitoldos.com.br 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
mogitoldos.com.br SEO score
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
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mogitoldos.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Mogitoldos.com.br 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.
mogitoldos.com.br
Open Graph data is detected on the main page of Mogi Toldos. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: