7.1 sec in total
651 ms
5.4 sec
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 651 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mec.gov.br performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value24.7 s
0/100
25%
Value22.7 s
0/100
10%
Value3,590 ms
1/100
30%
Value0.162
72/100
15%
Value46.0 s
0/100
10%
651 ms
166 ms
320 ms
467 ms
471 ms
Our browser made a total of 93 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, 8% (7 requests) were made to Youtube-nocookie.com and 6% (6 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Www.gov.br.
Page size can be reduced by 2.0 MB (28%)
7.4 MB
5.3 MB
In fact, the total size of Mec.gov.br main page is 7.4 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 6.4 MB which makes up the majority of the site volume.
Potential reduce by 276.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. This page needs HTML code to be minified as it can gain 102.5 kB, which is 33% 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 276.0 kB or 89% of the original size.
Potential reduce by 1.7 MB
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 1.7 MB 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 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 3.8 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 has all CSS files already compressed.
Number of requests can be reduced by 45 (57%)
79
34
The browser has sent 79 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 28 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
pt-br
651 ms
reset-cachekey-f334c7edf8b2dcb9035d2f670e50b2c1.css
166 ms
base-cachekey-bc9fd4d127f094da781880dddfcf906f.css
320 ms
resourceplone.app.jquerytools.dateinput-cachekey-831bc8cd16427648cf418ec8706ac97c.css
467 ms
resourceplone.formwidget.datetimestyles-cachekey-ab199c0dd942712ec3943f87e1097fac.css
471 ms
jquery.autocomplete-cachekey-03bc2c103288cf64b393d44f6c94c367.css
469 ms
embedder-cachekey-c98bdc6e383f35416bb806d62beda6de.css
474 ms
resourcecollective.pollscsscollective.polls-cachekey-de2d8d3fa8b2ffa8475825527ba652f6.css
469 ms
ploneCustom-cachekey-4382bfd70516a740fb2edb01ae95a090.css
474 ms
resourcebrasil.gov.tilesbrasilgovtiles-cachekey-07bf253808c4277ecdc1b79df15c9830.css
616 ms
resourcepas.plugins.loginunicologinunico-cachekey-84a51f29832d28ee2902ef739b6933e1.css
618 ms
swiper.min.css
39 ms
resourcelgpd.plugindsgov.min-cachekey-d3c5fe6e4c15cf10a0b266ff15e27cef.css
632 ms
resourcegovbr.policycanais-cachekey-89055d1bf2a9f53fa1dcace5229e84b8.css
623 ms
govbr.recom.9e3eea160cd9e43452ac.js
623 ms
resourceplone.app.jquery-cachekey-2c2a888cfcd8efa2ad65f29027f35a1d.js
625 ms
resourcegovbr.policyfolder_contents-cachekey-bb13175b0f001ce3ab78d181ef5c7e4f.js
763 ms
resourcegovbr.policycookiebar_1_3_55-cachekey-2e900bb944cceccc1f4a4adf9a8b537e.js
768 ms
resourcegovbr.policyapplication_cookiebar_1_3_55-cachekey-bf2e761d961c57718ae09d77f56e1002.js
774 ms
collective.js.jqueryui.custom.min-cachekey-5d67336f0ef52bb8c5dd85a66dacf1bd.js
939 ms
resourceplone.formwidget.recurrencejquery.tmpl-beta1-cachekey-84c0b53d37b8f5ffb6821017419b413d.js
784 ms
resourcecollective.js.bootstrapjsbootstrap.min-cachekey-856264eeda1b3def9d03ecf291269798.js
783 ms
resourcecollective.coverjsmain-cachekey-d53163ed9a1070f1ebcaca707c7b8af0.js
916 ms
resourcebrasil.gov.tilesvendorjquery.jplayer.min-cachekey-55c1207ace8c1fd6ec379f7a901ba442.js
920 ms
resourcedropdown-menu-cachekey-596d7b344a7fa8b93558004081cfd672.js
924 ms
swiper.min.js
47 ms
resourcelgpd.pluginchangeCookieImage-cachekey-8ac590aa8f328d9b6e2f00f8ba0ef38a.js
935 ms
resourcelgpd.pluginblock_cookies-cachekey-5b418d684afd798dbe0aaada96745f67.js
934 ms
resourcegovbr.policyclipboard.min-cachekey-f82e5405f0f32ba4be1b27667c52d06b.js
1065 ms
themegovbr.institucionaljslistar_autoridades_eagenda-cachekey-3ac58b5a728df6af3edaecebd77cb0c6.js
1070 ms
brasilgovagenda-720c34e.css
1075 ms
brasilgovagenda-720c34e.js
1091 ms
brasilgovportal-ee510e4.css
1084 ms
brasilgovportal-ee510e4.js
1088 ms
brasilgovtiles-7d5753d.css
1216 ms
brasilgovtiles-7d5753d.js
1235 ms
all.css
41 ms
sso-status-bar.js
1235 ms
govbrtheme-71a7413.css
1546 ms
vlibras-plugin.js
469 ms
lgpd_cookie_handling_1_3_87.js
1233 ms
govbrtheme-71a7413.js
1107 ms
vlibras-plugin.js
18 ms
govbr-logo-large.png
245 ms
b26be095-45e1-44b4-98b8-c5f6d30e0e45.png
1326 ms
79ee6e19-c0d8-41dc-8105-074b658ce189.png
1444 ms
5bfadd2a-623f-46cd-8b27-2bb3064262cc.png
1326 ms
51334189-eaf8-4817-a327-04c27cab51c0.png
247 ms
d87396b4-28b8-459d-9218-bee34be59beb.jpeg
687 ms
d6b02a24-e491-459e-b8a6-cd0c39b89c66.jpeg
762 ms
48ef134d-3dca-46a6-8dc4-51c3dc5d2856.jpeg
761 ms
5c0d60f8-bdd2-40ba-9074-d2da39964abf.png
760 ms
1c6e257e-ef9a-4328-be26-1128fa97aeb4.jpeg
1324 ms
c1ed5c86-8cd9-4626-bfe9-e069d2cd29cd.png
2108 ms
e1de1fb7-c624-44b1-9354-21781a60b1cb.png
2001 ms
7b583c21-a4cd-4701-9c70-8a3199053f6b.png
1879 ms
d14d07c3-1a80-4a4a-ac4a-fb862502e8be.jpeg
1328 ms
ed0383a8-3724-4f18-a8f3-8e4a4ae4e63d.png
1441 ms
5ecdeda8-1f0b-47f7-b2de-d824f4cdf9f5.png
1332 ms
c8693b20-5acf-4715-b665-dea972592bfc.jpeg
1580 ms
0d350753-c438-4711-9a7e-e9cd67ccd63a.png
2719 ms
0d1d969c-4280-4fcd-99e5-c6aa9e06e69c.jpeg
1513 ms
ac4a8247-e8f8-443d-9984-95d17dfbb82d.jpeg
1872 ms
1ffa1385-b11e-4dcd-aef4-fdbb52d7df6b.jpeg
1882 ms
ZxL_-sQLbd0
275 ms
BRgmnCxxE3g
712 ms
Fn7uCOUk9w8
711 ms
rawline-400.woff
1937 ms
rawline-500.woff
1941 ms
rawline-300.woff
2047 ms
rawline-200.woff
2048 ms
rawline-100.woff
2049 ms
rawline-600.woff
2215 ms
rawline-700.woff
2216 ms
rawline-800.woff
2215 ms
rawline-900.woff
2216 ms
fa-solid-900.ttf
184 ms
fa-regular-400.ttf
186 ms
govbr.png
2108 ms
fa-brands-400.ttf
440 ms
www-player.css
444 ms
www-embed-player.js
479 ms
base.js
543 ms
update.min.js
668 ms
spinner.gif
1593 ms
g5saOrWd5AVQT1PIm0b70pTp6wPS0RyhX4bW13q4Oa8.js
173 ms
embed.js
124 ms
Create
366 ms
Create
371 ms
Create
489 ms
GenerateIT
167 ms
GenerateIT
177 ms
GenerateIT
19 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
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: