9.4 sec in total
979 ms
7.3 sec
1.1 sec
Click here to check amazing Mec content for Brazil. Otherwise, check out these important facts you probably never knew about mec.gov.br
Seguimos garantindo a transparência! Mais informações: gov.br/mec.
Visit mec.gov.brWe analyzed Mec.gov.br page load time and found that the first response time was 979 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
mec.gov.br performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value17.4 s
0/100
25%
Value25.3 s
0/100
10%
Value5,700 ms
0/100
30%
Value0.162
72/100
15%
Value24.2 s
0/100
10%
979 ms
290 ms
440 ms
456 ms
453 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mec.gov.br, 12% (11 requests) were made to Youtube.com and 4% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Www.gov.br.
Page size can be reduced by 1.5 MB (34%)
4.3 MB
2.9 MB
In fact, the total size of Mec.gov.br main page is 4.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. 85% 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 3.4 MB which makes up the majority of the site volume.
Potential reduce by 247.2 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 89.9 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 247.2 kB or 88% of the original size.
Potential reduce by 920.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. Obviously, Mec needs image optimization as it can save up to 920.8 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 231 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 311.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. Mec.gov.br needs all CSS files to be minified and compressed as it can save up to 311.6 kB or 48% of the original size.
Number of requests can be reduced by 50 (68%)
74
24
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mec. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
pt-br
979 ms
reset-cachekey-cf78ce74a9e45755f37ba0095bbf6351.css
290 ms
base-cachekey-d2c705e98584706c08614172dd980a7b.css
440 ms
resourceplone.app.jquerytools.dateinput-cachekey-7e0fe89798ff06f283d117a85018c1fa.css
456 ms
resourceplone.formwidget.datetimestyles-cachekey-4b2f1cc3ae7ee9ac4a6fb27e74f556cd.css
453 ms
jquery.autocomplete-cachekey-cbee7d789c93c94be8050c757750a6cb.css
459 ms
embedder-cachekey-9bd8b3b09db8b709642d1ca5c8463f5c.css
458 ms
resourcecollective.pollscsscollective.polls-cachekey-435585ea1aed85e61c40aeba4ad10b43.css
457 ms
ploneCustom-cachekey-892953768b8cd996106e47bea3b1e4fb.css
584 ms
resourcebrasil.gov.tilesbrasilgovtiles-cachekey-ad448ae85ab4d6b6470667b0593250f5.css
590 ms
resourcepas.plugins.loginunicologinunico-cachekey-2cb6243c93ec04c9ebf2a319d5674ace.css
591 ms
swiper.min.css
43 ms
resourcelgpd.plugindsgov.min-cachekey-86c0d702348329b792306a4a01fd17d6.css
892 ms
resourcegovbr.policycanais-cachekey-6c4af847a3e93baf7db84def3f8d2420.css
583 ms
govbr.recom.9e3eea160cd9e43452ac.js
585 ms
resourceplone.app.jquery-cachekey-ae37d26a82ace36c5eb6a97436aca494.js
728 ms
resourcegovbr.policyfolder_contents-cachekey-e9ac0aad3a5ce1b1c696522b1937604e.js
730 ms
resourcegovbr.policycookiebar_1_3_55-cachekey-d18fb4033a43306e7b716a3884833e98.js
733 ms
resourcegovbr.policyapplication_cookiebar_1_3_55-cachekey-bb2a26c0ca1e73ee5103cbcc5e00a691.js
728 ms
collective.js.jqueryui.custom.min-cachekey-0ebb5ffb4d32aa6fe82913b3e87e579b.js
1323 ms
resourceplone.formwidget.recurrencejquery.tmpl-beta1-cachekey-44bb7bc5d68b172f1bca7b6c8e765687.js
884 ms
resourcecollective.js.bootstrapjsbootstrap.min-cachekey-71fdecb768988ef005bd6b9ceee2d712.js
875 ms
resourcecollective.coverjsmain-cachekey-0e4544a48c489503ab95320f1fa41687.js
1021 ms
resourcebrasil.gov.tilesvendorjquery.jplayer.min-cachekey-d876924e873ac383c3becc3273cd5026.js
1025 ms
resourcedropdown-menu-cachekey-348c5de0b92e9be8aafdfa1cd5256387.js
1020 ms
swiper.min.js
36 ms
resourcelgpd.pluginchangeCookieImage-cachekey-442ee20cf2bb48f7a34bd6d7a2d3e19f.js
1017 ms
resourcelgpd.pluginblock_cookies-cachekey-e29a18962c96ba303d001800505f8986.js
1018 ms
resourcegovbr.policyclipboard.min-cachekey-f37ea939f74fc22e2a38a2b6975667af.js
1155 ms
themegovbr.institucionaljslistar_autoridades_eagenda-cachekey-89cc166b4ce396a2a0f4cd9d42a04f6e.js
1155 ms
brasilgovagenda-720c34e.css
1159 ms
brasilgovagenda-720c34e.js
1169 ms
brasilgovportal-ee510e4.css
1164 ms
brasilgovportal-ee510e4.js
1303 ms
brasilgovtiles-7d5753d.css
1304 ms
brasilgovtiles-7d5753d.js
1468 ms
all.css
137 ms
sso-status-bar.js
1465 ms
govbrtheme-bf2e103.css
1760 ms
vlibras-plugin.js
469 ms
lgpd_cookie_handling_1_3_55.js
1351 ms
govbrtheme-bf2e103.js
1786 ms
vlibras-plugin.js
22 ms
govbr-logo-large.png
317 ms
10648559-04ef-427c-ac9c-6645ac65779c.jpeg
1490 ms
616d0702-2b7f-4bcd-b41e-24babef8a17d.png
434 ms
51334189-eaf8-4817-a327-04c27cab51c0.png
444 ms
e8209c6c-51c0-4f4f-ba72-0cd21d43346d.png
1723 ms
d80acec5-8563-44b5-9728-b98535859432.png
433 ms
ab7586b7-2830-45d1-a950-2aa0f878564f.jpeg
444 ms
1f705929-edeb-4b07-969d-e92b087a76a3.jpeg
1489 ms
edea83d7-0c5d-434f-8b30-5fa853231ec3.png
1550 ms
c1ed5c86-8cd9-4626-bfe9-e069d2cd29cd.png
3385 ms
e1de1fb7-c624-44b1-9354-21781a60b1cb.png
2428 ms
d38cffb7-e34a-4f4e-b820-29c9ce0907dd.jpeg
2348 ms
7b583c21-a4cd-4701-9c70-8a3199053f6b.png
3085 ms
cec00810-79b9-4cfb-b5e4-6b9edf530d3f.png
2347 ms
dp6g5u5PKp4
352 ms
TYmreZmdsoo
355 ms
UhrfNKPjouw
1392 ms
rawline-400.woff
2321 ms
rawline-500.woff
2321 ms
rawline-300.woff
2322 ms
rawline-200.woff
3278 ms
rawline-100.woff
2979 ms
rawline-600.woff
2616 ms
rawline-700.woff
2617 ms
rawline-800.woff
2972 ms
rawline-900.woff
2972 ms
fa-solid-900.ttf
1115 ms
fa-regular-400.ttf
1471 ms
govbr.png
3075 ms
fa-brands-400.ttf
1335 ms
www-player.css
1015 ms
www-embed-player.js
1053 ms
base.js
1291 ms
www-player.css
1113 ms
www-embed-player.js
1148 ms
base.js
1561 ms
update.min.js
629 ms
spinner.gif
2129 ms
ad_status.js
723 ms
id
286 ms
1xEiQfu-UCiwbMaFnr-G2Uzcd5udG06umsh6raawdbQ.js
488 ms
embed.js
378 ms
embed.js
308 ms
Create
621 ms
Create
617 ms
KFOmCnqEu92Fr1Mu4mxM.woff
286 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
532 ms
mec.gov.br 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
mec.gov.br 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
mec.gov.br 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
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
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mec.gov.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Mec.gov.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.
mec.gov.br
Open Graph data is detected on the main page of Mec. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: