9.8 sec in total
3.2 sec
6.4 sec
239 ms
Welcome to saire.pe.gov.br homepage info - get ready to check Saire PE best content for Brazil right away, or after learning these important things about saire.pe.gov.br
Visit saire.pe.gov.brWe analyzed Saire.pe.gov.br page load time and found that the first response time was 3.2 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
saire.pe.gov.br performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value9.1 s
1/100
25%
Value3.3 s
90/100
10%
Value100 ms
98/100
30%
Value0.003
100/100
15%
Value6.4 s
59/100
10%
3178 ms
352 ms
202 ms
143 ms
376 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 54% of them (52 requests) were addressed to the original Saire.pe.gov.br, 16% (15 requests) were made to Scontent.xx.fbcdn.net and 13% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Saire.pe.gov.br.
Page size can be reduced by 715.6 kB (67%)
1.1 MB
359.5 kB
In fact, the total size of Saire.pe.gov.br main page is 1.1 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. 55% of websites need less resources to load. CSS take 383.8 kB which makes up the majority of the site volume.
Potential reduce by 48.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 15.6 kB, which is 27% 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 48.2 kB or 85% of the original size.
Potential reduce by 112.0 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, Saire PE needs image optimization as it can save up to 112.0 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 220.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 220.3 kB or 71% of the original size.
Potential reduce by 335.1 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. Saire.pe.gov.br needs all CSS files to be minified and compressed as it can save up to 335.1 kB or 87% of the original size.
Number of requests can be reduced by 49 (60%)
82
33
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saire PE. 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 12 to 1 for CSS and as a result speed up the page load time.
saire.pe.gov.br
3178 ms
bootstrap.css
352 ms
font-awesome.css
202 ms
superfish.css
143 ms
megafish.css
376 ms
jquery.navgoco.css
167 ms
owl.carousel.css
154 ms
owl.theme.css
211 ms
style.css
445 ms
fancybox.css
278 ms
modernizr.custom.js
286 ms
jquery-1.11.2.min.js
449 ms
jquery.fancybox.pack.js
385 ms
bootstrap.min.js
331 ms
custom.js
331 ms
css
24 ms
css
37 ms
logo.png
218 ms
20160227033221.jpg
145 ms
20160224045008.jpg
172 ms
12705679_917727138326182_3013930123340363572_n.jpg
150 ms
12742045_915604725205090_126313438177335629_n.jpg
200 ms
20160217163222.jpg
206 ms
banner01.jpg
281 ms
prefeito.jpg
350 ms
nlt.png
267 ms
sdk.js
268 ms
quote.png
227 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
58 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
61 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
62 ms
Jzo62I39jc0gQRrbndN6nXYhjbSpvc47ee6xR_80Hnw.ttf
62 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
62 ms
mnpfi9pxYH-Go5UiibESIiZ2oysoEQEeKwjgmXLRnTc.ttf
62 ms
b9QBgL0iMZfDSpmcXcE8nPVE82mBoqAQeMZO1WdebIw.ttf
62 ms
Zd2E9abXLFGSr9G3YK2MsMEHkXu385rSv8spHqOuvSI.ttf
62 ms
b9QBgL0iMZfDSpmcXcE8nBPtpc1JAjij63Hi_JcAPQ4.ttf
62 ms
fontawesome-webfont.woff
374 ms
superfish.min.js
170 ms
jquery.navgoco.min.js
249 ms
owl.carousel.min.js
248 ms
jquery.ticker.js
249 ms
site.js
247 ms
masonry.pkgd.min.js
359 ms
imagesloaded.js
294 ms
jquery.zaccordion.min.js
330 ms
matchMedia.js
309 ms
matchMedia.addListener.js
309 ms
enquire.min.js
360 ms
waypoints.js
363 ms
waypoints-sticky.js
369 ms
mg0cGfGRUERshzBlvqxeAJBzG2WrWg1L9nqu73HZFmCglnMp3_3A8V8Ai8YosRtX.ttf
17 ms
BP5K8ZAJv9qEbmuFp8RpJcetkHQYAjN25HtR17zqnK4.ttf
15 ms
mg0cGfGRUERshzBlvqxeADnTZvQ8ze_XKQkA_t0TXkiglnMp3_3A8V8Ai8YosRtX.ttf
16 ms
superfish.min.js
204 ms
130 ms
xd_arbiter.php
212 ms
xd_arbiter.php
423 ms
jquery.navgoco.min.js
59 ms
page.php
138 ms
owl.carousel.min.js
68 ms
jquery.ticker.js
60 ms
o_zjiOVHPPW.css
312 ms
_rx8naC75Dy.js
418 ms
t-KLv3gqZy0.js
485 ms
pHhwt9caQAA.js
619 ms
site.js
72 ms
masonry.pkgd.min.js
53 ms
imagesloaded.js
58 ms
jquery.zaccordion.min.js
62 ms
matchMedia.js
58 ms
matchMedia.addListener.js
73 ms
enquire.min.js
56 ms
waypoints.js
69 ms
waypoints-sticky.js
95 ms
10487178_1432011820412060_5127772922539213916_n.jpg
421 ms
10509665_1432002370413005_986559158921795209_n.jpg
528 ms
12734156_1117382698274105_2342969952352990543_n.jpg
654 ms
12705556_1199384280089413_8022840845251041638_n.jpg
805 ms
1915621_1070798926285908_6744100413018379428_n.jpg
669 ms
12790883_1053805767973989_1164847711758736985_n.jpg
624 ms
12743648_106602459730541_5367438714388781882_n.jpg
818 ms
12106983_1667292370210415_6567022484428813673_n.jpg
725 ms
12729345_144281249290851_3639798326187656022_n.jpg
1237 ms
12573962_941384222597013_4119072478863383038_n.jpg
778 ms
12742112_423856247824597_608093975875572914_n.jpg
736 ms
12063870_1611393769122422_1123371138977078327_n.jpg
841 ms
9204_1031394526923051_501387270869518857_n.jpg
845 ms
11880387_1664457580432971_5293877953761658801_n.jpg
845 ms
12745492_209985676020192_2599558694939999340_n.jpg
930 ms
wL6VQj7Ab77.png
72 ms
CSXXCvknpgK.png
72 ms
R9a_DtVRZgv.js
69 ms
cUDgRFxaoIk.js
70 ms
0JBr1QHp8Gi.js
72 ms
kDOzhTr2W91.js
134 ms
saire.pe.gov.br accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role] values are not valid
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
Image elements do not have [alt] attributes
Links do not have a discernible name
saire.pe.gov.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
saire.pe.gov.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Tap targets are not sized appropriately
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Saire.pe.gov.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Saire.pe.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.
saire.pe.gov.br
Open Graph description is not detected on the main page of Saire PE. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: