3.2 sec in total
425 ms
1.9 sec
936 ms
Click here to check amazing Search Vivalocal content for Brazil. Otherwise, check out these important facts you probably never knew about search.vivalocal.com
Visit search.vivalocal.comWe analyzed Search.vivalocal.com page load time and found that the first response time was 425 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
search.vivalocal.com performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value5.4 s
20/100
25%
Value1.7 s
100/100
10%
Value680 ms
44/100
30%
Value0
100/100
15%
Value7.0 s
53/100
10%
425 ms
19 ms
34 ms
11 ms
81 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Search.vivalocal.com, 16% (7 requests) were made to Ww684.smartadserver.com and 14% (6 requests) were made to Static.viva-images.com. The less responsive or slowest element that took the longest time to load (517 ms) relates to the external source Ww684.smartadserver.com.
Page size can be reduced by 681.1 kB (73%)
936.9 kB
255.8 kB
In fact, the total size of Search.vivalocal.com main page is 936.9 kB. 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. Javascripts take 655.6 kB which makes up the majority of the site volume.
Potential reduce by 124.5 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 16.7 kB, which is 11% 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 124.5 kB or 83% of the original size.
Potential reduce by 517 B
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. Search Vivalocal images are well optimized though.
Potential reduce by 456.8 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 456.8 kB or 70% of the original size.
Potential reduce by 99.3 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. Search.vivalocal.com needs all CSS files to be minified and compressed as it can save up to 99.3 kB or 86% of the original size.
Number of requests can be reduced by 25 (61%)
41
16
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Search Vivalocal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
search.vivalocal.com
425 ms
prepend_b.js
19 ms
captions.php
34 ms
summary_br_latam.css
11 ms
show_ads.js
81 ms
async-ads.js
80 ms
show_afs_ads.js
80 ms
app_b.js
59 ms
compatibility_b.js
59 ms
166 ms
global_brazil.gif
23 ms
global_street.gif
23 ms
90 ms
aip
139 ms
ca-pub-1778014916682445.js
204 ms
zrt_lookup.html
200 ms
show_ads_impl.js
115 ms
ads
268 ms
171 ms
ads
296 ms
osd.js
11 ms
ads
227 ms
async-ads.js
140 ms
iframe.html
186 ms
aip
165 ms
aip
517 ms
aip
504 ms
gtm.js
102 ms
1.jpg
107 ms
1.jpg
422 ms
1.jpg
91 ms
m_js_controller.js
358 ms
abg.js
380 ms
analytics.js
47 ms
bk-coretag.js
78 ms
googlelogo_color_112x36dp.png
76 ms
nessie_icon_tiamat_white.png
16 ms
x_button_blue2.png
33 ms
s
24 ms
collect
36 ms
collect
97 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
8 ms
29021
30 ms
ui
15 ms
search.vivalocal.com accessibility score
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
Links do not have a discernible name
search.vivalocal.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
search.vivalocal.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Search.vivalocal.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Search.vivalocal.com 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.
search.vivalocal.com
Open Graph description is not detected on the main page of Search Vivalocal. 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: