8 sec in total
1.1 sec
6.6 sec
297 ms
Welcome to fanap.br homepage info - get ready to check Fanap best content for Brazil right away, or after learning these important things about fanap.br
Visit fanap.brWe analyzed Fanap.br page load time and found that the first response time was 1.1 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fanap.br performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value14.0 s
0/100
25%
Value17.4 s
0/100
10%
Value150 ms
94/100
30%
Value0.155
74/100
15%
Value23.2 s
1/100
10%
1112 ms
690 ms
1240 ms
829 ms
968 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 41% of them (35 requests) were addressed to the original Fanap.br, 16% (14 requests) were made to Maps.googleapis.com and 11% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Fanap.br.
Page size can be reduced by 1.3 MB (39%)
3.4 MB
2.1 MB
In fact, the total size of Fanap.br main page is 3.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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 32.4 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 7.4 kB, which is 18% 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 32.4 kB or 79% of the original size.
Potential reduce by 28.2 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. Fanap images are well optimized though.
Potential reduce by 767.1 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 767.1 kB or 69% of the original size.
Potential reduce by 488.9 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. Fanap.br needs all CSS files to be minified and compressed as it can save up to 488.9 kB or 86% of the original size.
Number of requests can be reduced by 53 (69%)
77
24
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fanap. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
fanap.br
1112 ms
normalize.css
690 ms
bootstrap.min.css
1240 ms
font-awesome.min.css
829 ms
animate.min.css
968 ms
hover-min.css
1256 ms
template.css
973 ms
jquery.fancybox.css
1121 ms
jquery.fancybox-buttons.css
1123 ms
head.min.js
1526 ms
jquery.min.js
1253 ms
bootstrap.min.js
969 ms
owl.carousel.min.js
899 ms
bootstrap-portfilter.min.js
437 ms
template.js
436 ms
jquery.fancybox.js
1026 ms
jquery.fancybox-buttons.js
986 ms
logo-frase.gif
1275 ms
ISEDUC.jpg
2411 ms
MBALOG.jpg
3234 ms
ContFiscTrib.jpg
3098 ms
inf-cal.png
1565 ms
inf-NPJ.png
1795 ms
inf-ProcSel.png
1957 ms
inf-Hor.png
2261 ms
inf-NAPA.png
2353 ms
inf-Biblio.png
2512 ms
EaD.jpg
3229 ms
revistas.jpg
3479 ms
foto-not-audit.jpg
3116 ms
prev-evento.jpg
3340 ms
foto-not-previ-diadamulher.jpg
4089 ms
b-destaque-aud.jpg
3939 ms
iMw4ly_SU5g
112 ms
fontawesome-webfont.woff
4333 ms
glyphicons-halflings-regular.woff
4041 ms
sdk.js
199 ms
maps
48 ms
embed
215 ms
www-embed-player-vflfNyN_r.css
70 ms
www-embed-player.js
121 ms
base.js
193 ms
236 ms
js
201 ms
init_embed.js
181 ms
xd_arbiter.php
196 ms
xd_arbiter.php
347 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
43 ms
ad_status.js
114 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
130 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
142 ms
common.js
59 ms
map.js
72 ms
google4.png
123 ms
overlay.js
38 ms
util.js
122 ms
onion.js
115 ms
search_impl.js
120 ms
StaticMapService.GetMapImage
287 ms
stats.js
110 ms
openhand_8_8.cur
81 ms
ViewportInfoService.GetViewportInfo
75 ms
ViewportInfoService.GetViewportInfo
89 ms
kh
196 ms
transparent.png
133 ms
kh
155 ms
controls.js
20 ms
kh
164 ms
kh
164 ms
kh
171 ms
ViewportInfoService.GetViewportInfo
103 ms
vt
122 ms
css
135 ms
vt
135 ms
vt
134 ms
vt
136 ms
entity11.png
71 ms
vt
138 ms
mapcnt6.png
71 ms
vt
86 ms
vt
120 ms
tmapctrl.png
51 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
17 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
21 ms
AuthenticationService.Authenticate
27 ms
fanap.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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
fanap.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fanap.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
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanap.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 Fanap.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.
fanap.br
Open Graph description is not detected on the main page of Fanap. 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: