3 sec in total
496 ms
2.2 sec
318 ms
Welcome to viviscal.pt homepage info - get ready to check Viviscal best content right away, or after learning these important things about viviscal.pt
Nós de Viviscal oferecemos uma série de produtos clinicamente pesquisados, sem drogas, que deixam os cabelos mais grossos e cheios para as mulheres e homens. Nossa missão como uma empresa de saúde que...
Visit viviscal.ptWe analyzed Viviscal.pt page load time and found that the first response time was 496 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
viviscal.pt performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value12.7 s
0/100
25%
Value14.9 s
1/100
10%
Value24,040 ms
0/100
30%
Value0.003
100/100
15%
Value45.9 s
0/100
10%
496 ms
15 ms
142 ms
108 ms
70 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 84% of them (83 requests) were addressed to the original Viviscal.pt, 3% (3 requests) were made to W2.yotpo.com and 2% (2 requests) were made to Js.maxmind.com. The less responsive or slowest element that took the longest time to load (843 ms) belongs to the original domain Viviscal.pt.
Page size can be reduced by 1.9 MB (48%)
3.9 MB
2.0 MB
In fact, the total size of Viviscal.pt main page is 3.9 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. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 91.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. 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 91.5 kB or 81% of the original size.
Potential reduce by 955.9 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, Viviscal needs image optimization as it can save up to 955.9 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 465.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 465.1 kB or 76% of the original size.
Potential reduce by 343.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. Viviscal.pt needs all CSS files to be minified and compressed as it can save up to 343.6 kB or 89% of the original size.
Number of requests can be reduced by 37 (41%)
91
54
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viviscal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.viviscal.pt
496 ms
geoip2.js
15 ms
aa3413af527984cba308e8a2450e8531.css
142 ms
prototype.js
108 ms
ccard.js
70 ms
validation.js
72 ms
builder.js
70 ms
effects.js
172 ms
dragdrop.js
135 ms
controls.js
136 ms
slider.js
170 ms
js.js
174 ms
form.js
208 ms
menu.js
205 ms
translate.js
201 ms
cookies.js
203 ms
jquery-1.7.2.min.js
235 ms
jquery-noconflict.js
252 ms
jquery.owlcarousel.min.js
272 ms
jquery.easing.min.js
266 ms
jquery.accordion.min.js
267 ms
lightbox.js
270 ms
geoip2.js
303 ms
jquery.tabs.min.js
321 ms
jquery.ba-throttle-debounce.min.js
342 ms
tinybox_new.js
333 ms
minor.js
343 ms
simpletabs_1.3.packed.js
337 ms
accordion.js
371 ms
accordion_menu.js
393 ms
hoverIntent.js
398 ms
superfish.js
402 ms
jquery-accordion-menu.js
408 ms
jquery.flexslider.js
423 ms
flexslider.css
440 ms
me
52 ms
widget.js
93 ms
speechBubble.png
91 ms
Viviscal-logo-PT.png
93 ms
vpt_25yearlogo.png
92 ms
Viviscal_Female_Supps_1_pack_PT_113x113.png
149 ms
Viviscal_Shampoo_113x113.png
152 ms
Viviscal_Conditioner_113x113.png
171 ms
Viviscal_Elixir_113x113.png
230 ms
Viviscal_Fibers_for_Women_113x113.png
229 ms
Viviscal_Offers_for_Women_PT_h113.png
250 ms
Viviscal_Male_Supps_1_pack_PT_113x113.png
301 ms
Viviscal_Fibers_for_Men_113x113.png
308 ms
Viviscal_Offers_for_Men_PT_h113.png
319 ms
whyMolecule.jpg
293 ms
nav_hairstrand_1.jpg
292 ms
nav_moneyback.jpg
321 ms
nav_drR.jpg
386 ms
nav_stylistR.jpg
371 ms
nav_realusers.jpg
386 ms
AW-239_Viviscal_Web_PTBanner_1200x358px.jpg
615 ms
Banner_Portugal_1200x416_-AW_202_309.jpg
585 ms
3717.1_Underbannerblurb_Image_PT.jpg
474 ms
Viviscal_Female_Supps_1_pack_PT_110x209.jpg
479 ms
Viviscal_Male_Supps_1_pack_PT_110x209.jpg
477 ms
5stars.jpg
475 ms
molecules.png
546 ms
adrienne_pt.png
632 ms
christina_pt.png
668 ms
jessica_pt.png
661 ms
kristie_pt.png
733 ms
lissa_pt.png
746 ms
patty_pt.png
791 ms
samantha_pt.png
809 ms
smallLine.gif
734 ms
GStevensB.png
734 ms
ga.js
16 ms
Gwyneth_Paltrow.png
843 ms
icon_fb.png
786 ms
__utm.gif
22 ms
icon_yt.png
725 ms
icon_phone.png
730 ms
1e25c4c8-80d6-44ba-bc21-51daaa0cd556.woff
806 ms
widget.css
228 ms
collect
53 ms
icon_mail.png
733 ms
l2glogo.jpg
729 ms
ga-audiences
33 ms
headerBottom.jpg
713 ms
shoppingCart.png
656 ms
hokiBulletPoint.gif
709 ms
css
24 ms
press-bg.jpg
591 ms
seal_1143307.js
90 ms
gtm.js
65 ms
cbg_w.png
45 ms
i
20 ms
batch
87 ms
slider-arrows.png
475 ms
opener.png
469 ms
sign_in_url
6 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
9 ms
c278ce72e006b028117eb5786432baf4.css
45 ms
bg_direction_nav.png
71 ms
viviscal.pt 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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
viviscal.pt 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
viviscal.pt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Viviscal.pt 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 Viviscal.pt 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.
viviscal.pt
Open Graph description is not detected on the main page of Viviscal. 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: