7 sec in total
568 ms
5.9 sec
572 ms
Welcome to vitally.com.br homepage info - get ready to check Vitally best content for Brazil right away, or after learning these important things about vitally.com.br
Testados e aprovados por profissionais.
Visit vitally.com.brWe analyzed Vitally.com.br page load time and found that the first response time was 568 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.
vitally.com.br performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value23.1 s
0/100
25%
Value19.6 s
0/100
10%
Value2,790 ms
3/100
30%
Value0.818
4/100
15%
Value42.1 s
0/100
10%
568 ms
579 ms
70 ms
148 ms
288 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 55% of them (64 requests) were addressed to the original Vitally.com.br, 10% (12 requests) were made to Fonts.gstatic.com and 9% (11 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Vitally.ind.br.
Page size can be reduced by 724.4 kB (16%)
4.6 MB
3.8 MB
In fact, the total size of Vitally.com.br main page is 4.6 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. 70% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 52.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 21.0 kB, which is 34% 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 52.0 kB or 84% of the original size.
Potential reduce by 96.5 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. Vitally images are well optimized though.
Potential reduce by 448.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 448.3 kB or 73% of the original size.
Potential reduce by 127.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. Vitally.com.br needs all CSS files to be minified and compressed as it can save up to 127.6 kB or 81% of the original size.
Number of requests can be reduced by 44 (46%)
96
52
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vitally. 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 12 to 1 for CSS and as a result speed up the page load time.
vitally.com.br
568 ms
www.vitally.com.br
579 ms
css
70 ms
bootstrap.min.css
148 ms
bootstrap-select.min.css
288 ms
reset.css
286 ms
slick.css
290 ms
estilos.css
296 ms
malerta.css
290 ms
bootstrap.alerts.min.css
292 ms
font-awesome.min.css
32 ms
jquery-1.11.2.min.js
713 ms
perfect-scrollbar.jquery.min.js
436 ms
perfect-scrollbar.min.js
445 ms
slick.min.js
463 ms
jquery.malerta-0.1.js
461 ms
jquery.tools.validator.min.js
462 ms
jquery.maskedinput.1.3.1.min.js
583 ms
jquery-cookie.js
606 ms
perfect.js
614 ms
site.js
616 ms
bootstrap-select.min.js
614 ms
bootstrap.min.js
732 ms
modernizr.js
743 ms
bootstrap-select.min.js
755 ms
spritespin.js
801 ms
mapa.js
758 ms
analytics.js
42 ms
hotjar-115518.js
102 ms
hamburguer-abrir.png
654 ms
vitally-logotipo-2.png
712 ms
exemplo-img-menu.jpg
722 ms
start.jpg
1167 ms
hold.jpg
1026 ms
milenium-iii.jpg
1315 ms
loft.jpg
1112 ms
impact.jpg
1428 ms
concept.jpg
1294 ms
convergent-six.jpg
1455 ms
down-icon.png
1267 ms
055807_banner-combo-start-2.jpg
2593 ms
055906_combo-convergent-six.jpg
2621 ms
impact-360.jpg
2148 ms
linha-basquete.jpg
2103 ms
carrinho-icon-produto.png
1568 ms
370_370_crossmith.jpg
1603 ms
fechar-mapa.jpg
1713 ms
fechar.png
1744 ms
sdk.js
193 ms
top-icon.png
1831 ms
linkid.js
10 ms
ec.js
10 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
75 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
80 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
101 ms
Jzo62I39jc0gQRrbndN6nXYhjbSpvc47ee6xR_80Hnw.ttf
95 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
100 ms
mnpfi9pxYH-Go5UiibESIiZ2oysoEQEeKwjgmXLRnTc.ttf
101 ms
t6Nd4cfPRhZP44Q5QAjcCywlidHJgAgmTjOEEzwu1L8.ttf
174 ms
bmC0pGMXrhphrZJmniIZpSwlidHJgAgmTjOEEzwu1L8.ttf
100 ms
OLffGBTaF0XFOW1gnuHF0SwlidHJgAgmTjOEEzwu1L8.ttf
167 ms
W4wDsBUluyw0tK3tykhXEXYhjbSpvc47ee6xR_80Hnw.ttf
166 ms
7m8l7TlFO-S3VkhHuR0atywlidHJgAgmTjOEEzwu1L8.ttf
165 ms
12mE4jfMSBTmg-81EiS-YcDdSZkkecOE1hvV7ZHvhyU.ttf
167 ms
fontawesome-webfont.woff
44 ms
server.php
547 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
167 ms
31-anos.jpg
1771 ms
modal.png
1869 ms
atendimento_vitally.png
1890 ms
bg-banner.png
1996 ms
a-vitally.jpg
2745 ms
126 ms
desde-1978.jpg
1976 ms
xd_arbiter.php
156 ms
xd_arbiter.php
370 ms
onde-encontrar.jpg
2552 ms
mapa.jpg
2637 ms
right-icon-small.png
2089 ms
whatsapp.png
3193 ms
popup.jpg
2340 ms
collect
14 ms
collect
50 ms
www.vitally.com.br
2328 ms
prev-icon-banner.png
2259 ms
next-icon-banner.png
2354 ms
ajax-loader.gif
2445 ms
whatsapp-green.png
2404 ms
slick.woff
2481 ms
style.css
69 ms
server.php
3742 ms
ga-audiences
41 ms
page.php
128 ms
ebiMDO3r-8l.css
170 ms
jGc-59L_9lo.css
211 ms
q68gy-v_YMF.js
293 ms
VvsfEObxnnn.js
367 ms
0wM5s1Khldu.js
312 ms
1bNoFZUdlYZ.js
312 ms
12717919_1128040887230205_1456032464539550879_n.jpg
334 ms
10450810_920154378018858_3436335577235781428_n.png
423 ms
12316555_787491694706505_2897881124516981544_n.jpg
453 ms
10320526_1673990379549794_1195656749214162129_n.jpg
454 ms
12193648_1151967738165657_6522037960504605970_n.jpg
455 ms
11012871_1704772013083199_442268329500910590_n.jpg
490 ms
12391120_735906269886956_1847669484957591767_n.jpg
456 ms
12391909_1006527966070209_4683009190391956135_n.jpg
504 ms
12239751_469353999914711_5508183727493450852_n.jpg
493 ms
12743900_791035940997486_8433672842805847099_n.jpg
553 ms
12376493_1107547362589397_7192720076065428951_n.jpg
544 ms
wL6VQj7Ab77.png
48 ms
s7jcwEQH7Sx.png
48 ms
I6-MnjEovm5.js
47 ms
pQrUxxo5oQp.js
41 ms
slick.ttf
555 ms
slick.svg
195 ms
vitally.com.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
vitally.com.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
Page has valid source maps
vitally.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Vitally.com.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 Vitally.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.
vitally.com.br
Open Graph description is not detected on the main page of Vitally. 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: