19 sec in total
6.1 sec
11.8 sec
1.1 sec
Visit ezb.com.br now to see the best up-to-date EZB content and also check out these interesting facts you probably never knew about ezb.com.br
| Ph.D. CIÊNCIAS DA COMUNICAÇÃO | PESQUISADOR | PROFESSOR | PALESTRANTE | CURIOSO
Visit ezb.com.brWe analyzed Ezb.com.br page load time and found that the first response time was 6.1 sec and then it took 12.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ezb.com.br performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value2.0 s
97/100
25%
Value3.6 s
87/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
6067 ms
1331 ms
916 ms
953 ms
923 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 52% of them (78 requests) were addressed to the original Ezb.com.br, 18% (27 requests) were made to Google.com and 9% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Ezb.com.br.
Page size can be reduced by 2.3 MB (56%)
4.1 MB
1.8 MB
In fact, the total size of Ezb.com.br main page is 4.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. 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. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 40.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 40.0 kB or 78% of the original size.
Potential reduce by 1.1 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, EZB needs image optimization as it can save up to 1.1 MB or 45% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 798.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 798.1 kB or 69% of the original size.
Potential reduce by 376.7 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. Ezb.com.br needs all CSS files to be minified and compressed as it can save up to 376.7 kB or 82% of the original size.
Number of requests can be reduced by 76 (55%)
139
63
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EZB. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
ezb.com.br
6067 ms
bootstrap.css
1331 ms
responsive.css
916 ms
camera.css
953 ms
style.css
923 ms
flexslider.css
616 ms
owl.carousel.css
584 ms
owl.theme.css
726 ms
font-awesome.css
8 ms
cherry-plugin.css
1086 ms
styles.css
960 ms
main-style.css
1072 ms
magnific-popup.css
929 ms
css
28 ms
css
41 ms
theme.css
1342 ms
bootstrap-grid.min.css
1117 ms
jquery-1.7.2.min.js
3917 ms
jquery.easing.1.3.js
1239 ms
jquery.elastislide.js
1253 ms
js
26 ms
jquery-migrate-1.2.1.min.js
3624 ms
swfobject.js
1390 ms
modernizr.js
3641 ms
jflickrfeed.js
3608 ms
custom.js
3635 ms
bootstrap.min.js
2456 ms
motopress-ce-custom.css
2489 ms
jquery.mobile.customized.min.js
3480 ms
comment-reply.min.js
3368 ms
jquery.flexslider-min.js
3356 ms
cherry-plugin.js
3394 ms
jquery.form.min.js
3421 ms
scripts.js
3420 ms
jquery.mousewheel-3.0.4.js
3543 ms
scrollShowTime.js
3542 ms
device.js
3543 ms
themeScript.js
3564 ms
superfish.js
3585 ms
jquery.mobilemenu.js
3692 ms
jquery.magnific-popup.min.js
3730 ms
jplayer.playlist.min.js
3530 ms
jquery.jplayer.min.js
3659 ms
tmstickup.js
3397 ms
jquery.zaccordion.min.js
3388 ms
camera.min.js
3514 ms
jquery.debouncedresize.js
3437 ms
jquery.ba-resize.min.js
3336 ms
jquery.isotope.js
3340 ms
wp-emoji-release.min.js
3105 ms
style.css
3160 ms
css
15 ms
css
24 ms
css
23 ms
css
23 ms
css
20 ms
css
24 ms
css
27 ms
style.css
159 ms
bg-part.png
269 ms
topo1.jpg
816 ms
extra-item1.png
259 ms
titulo_logo.png
896 ms
foto_ado.png
810 ms
embed
223 ms
extra-item4.png
428 ms
extra-item6.png
431 ms
extra-item3.png
419 ms
extra-item5.png
489 ms
loading_32.gif
550 ms
loading_bg_32.png
553 ms
Palestras_01-388x218.jpg
733 ms
Palestras_02-388x218.jpg
735 ms
Palestras_03-388x218.jpg
734 ms
Palestras_04-388x218.jpg
936 ms
Palestras_05B-388x218.jpg
938 ms
Palestras_06-388x218.jpg
937 ms
Palestras_07A-388x218.jpg
938 ms
Palestras_08B-388x218.jpg
949 ms
Palestras_09-388x218.jpg
978 ms
icon1.png
1118 ms
icon3.png
1119 ms
icon2.png
1120 ms
_xyN3apAT_yRRDeqB3sPRg.woff
62 ms
OsJ2DjdpjqFRVUSto6IffD8E0i7KZn-EPnyo3HZu7kw.woff
127 ms
_aijTyevf54tkVDLy-dlnD8E0i7KZn-EPnyo3HZu7kw.woff
129 ms
0ihfXUL2emPh0ROJezvraD8E0i7KZn-EPnyo3HZu7kw.woff
127 ms
w5P-SI7QJQSDqB3GziL8XT8E0i7KZn-EPnyo3HZu7kw.woff
128 ms
8Usm7f8XTsZinW2e-ZMd5fesZW2xOQ-xsNqO47m55DA.woff
125 ms
analytics.js
76 ms
js
214 ms
init_embed.js
211 ms
collect
120 ms
loading_16.gif
660 ms
loading_bg_16.png
668 ms
ajax-loader.gif
715 ms
bg-part2.png
800 ms
extra_bg_image_1.jpg
824 ms
padrao_bg_publicacoes.png
849 ms
common.js
59 ms
map.js
60 ms
google4.png
109 ms
overlay.js
105 ms
util.js
100 ms
onion.js
98 ms
search_impl.js
100 ms
stats.js
53 ms
openhand_8_8.cur
79 ms
ViewportInfoService.GetViewportInfo
101 ms
ViewportInfoService.GetViewportInfo
64 ms
kh
88 ms
kh
40 ms
transparent.png
36 ms
controls.js
23 ms
css
151 ms
entity11.png
46 ms
mapcnt6.png
104 ms
vt
158 ms
vt
168 ms
vt
194 ms
vt
162 ms
vt
141 ms
vt
164 ms
vt
201 ms
vt
187 ms
vt
198 ms
vt
206 ms
vt
208 ms
vt
245 ms
vt
260 ms
vt
252 ms
vt
248 ms
vt
262 ms
vt
255 ms
vt
297 ms
vt
297 ms
vt
300 ms
vt
316 ms
vt
315 ms
vt
313 ms
vt
348 ms
vt
353 ms
vt
362 ms
tmapctrl.png
48 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
29 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
38 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
40 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
49 ms
AuthenticationService.Authenticate
34 ms
extra-item2.png
152 ms
ohKfORL_YnhBMzkCPoIqwobN6UDyHWBl620a-IRfuBk.woff
5 ms
ezb.com.br accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
ezb.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
ezb.com.br SEO score
N/A
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ezb.com.br can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Portuguese. Our system also found out that Ezb.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.
ezb.com.br
Open Graph description is not detected on the main page of EZB. 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: