3.8 sec in total
175 ms
3.5 sec
183 ms
Visit sensodyne.com.ar now to see the best up-to-date Sensodyne content for Argentina and also check out these interesting facts you probably never knew about sensodyne.com.ar
Cepillándote los dientes dos veces por día, Sensodyne ofrece alivio duradero para la sensibilidad dental. Aprendé más sobre la crema dental #1 recomendada por odontólogos para dientes sensibles.
Visit sensodyne.com.arWe analyzed Sensodyne.com.ar page load time and found that the first response time was 175 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
sensodyne.com.ar performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value7.8 s
3/100
25%
Value6.7 s
35/100
10%
Value1,430 ms
15/100
30%
Value0.371
29/100
15%
Value14.0 s
10/100
10%
175 ms
2193 ms
372 ms
247 ms
309 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 26% of them (35 requests) were addressed to the original Sensodyne.com.ar, 65% (87 requests) were made to Sensodyne.es and 3% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Sensodyne.com.ar.
Page size can be reduced by 268.8 kB (41%)
651.2 kB
382.4 kB
In fact, the total size of Sensodyne.com.ar main page is 651.2 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. 30% of websites need less resources to load. Images take 285.7 kB which makes up the majority of the site volume.
Potential reduce by 66.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 13.6 kB, which is 16% 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 66.4 kB or 80% of the original size.
Potential reduce by 12.7 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. Sensodyne images are well optimized though.
Potential reduce by 112.4 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 112.4 kB or 58% of the original size.
Potential reduce by 77.4 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. Sensodyne.com.ar needs all CSS files to be minified and compressed as it can save up to 77.4 kB or 89% of the original size.
Number of requests can be reduced by 64 (74%)
87
23
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sensodyne. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
sensodyne.com.ar
175 ms
www.sensodyne.com.ar
2193 ms
styles.css
372 ms
ar.css
247 ms
jquery-1.7.min.js
309 ms
swfobject.js
290 ms
supersleight.plugin.js
392 ms
main.js
467 ms
home-page-features.css
491 ms
homepage.js
447 ms
Bootstrap.js
9 ms
ga.js
90 ms
ar.gif
197 ms
mx.gif
132 ms
ng.gif
197 ms
bg.gif
212 ms
mobile-menu-icon.gif
197 ms
logo.gif
199 ms
mobile-globe-icon.gif
196 ms
gsk-logo.gif
234 ms
main-nav-bg-left.gif
259 ms
nav-bg-right.gif
305 ms
body-bg-left.png
324 ms
body-bg-right.png
329 ms
sensodyne_complete_protection_powered_by_novamin.png
329 ms
sensodyne-complete.png
403 ms
tooth.png
466 ms
cuadirto_web-01.png
474 ms
pl.gif
189 ms
pr.gif
193 ms
au.gif
173 ms
at.gif
174 ms
be.gif
174 ms
br.gif
175 ms
ca.gif
176 ms
cl.gif
206 ms
cn.gif
213 ms
co.gif
215 ms
dk.gif
215 ms
fi.gif
217 ms
fr.gif
219 ms
de.gif
240 ms
gr.gif
241 ms
in.gif
246 ms
id.gif
247 ms
ie.gif
247 ms
it.gif
258 ms
jp.gif
275 ms
lb.gif
276 ms
my.gif
280 ms
nl.gif
281 ms
no.gif
281 ms
pk.gif
299 ms
pe.gif
308 ms
ph.gif
308 ms
pt.gif
316 ms
ro.gif
319 ms
ru.gif
320 ms
sa.gif
340 ms
sg.gif
341 ms
za.gif
341 ms
es.gif
345 ms
se.gif
346 ms
ch.gif
347 ms
tw.gif
381 ms
serverComponent.php
101 ms
bg_sensodyne_complete.jpg
398 ms
btn-learnMore.png
396 ms
btn-learnMore-cap.png
416 ms
label-new-bg.gif
427 ms
label-new-cap.png
502 ms
sensodyne_complete_right_gradient.jpg
509 ms
sensodyne_complete_carousel_sensitive_layer.png
510 ms
sensodyne_complete_small_carousel_layers.png
549 ms
home-content-bg.gif
553 ms
footer-nav-bullet.gif
561 ms
PragmaticaExtraLight.woff
576 ms
PragmaticaLight.woff
619 ms
__utm.gif
15 ms
__utm.gif
5 ms
__utm.gif
5 ms
78e5a798441ce3ca03679ac4c81347ed.js
13 ms
quant.js
17 ms
pixel;r=1999679647;a=p-8bY7VlOzTYlNA;fpan=1;fpa=P0-1409431375-1458278545619;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458278545619;tzo=-180;ref=;url=http%3A%2F%2Fwww.sensodyne.com.ar%2F;ogl=
16 ms
au.gif
47 ms
at.gif
49 ms
be.gif
60 ms
br.gif
68 ms
ca.gif
70 ms
s53648771576117
8 ms
ar.gif
66 ms
th.gif
200 ms
tr.gif
203 ms
uae.gif
213 ms
uk.gif
210 ms
us.gif
214 ms
vn.gif
234 ms
cl.gif
46 ms
cn.gif
49 ms
co.gif
62 ms
dk.gif
63 ms
fi.gif
65 ms
fr.gif
63 ms
de.gif
45 ms
gr.gif
48 ms
in.gif
72 ms
id.gif
62 ms
ie.gif
64 ms
it.gif
59 ms
jp.gif
50 ms
lb.gif
49 ms
my.gif
61 ms
nl.gif
64 ms
no.gif
72 ms
pk.gif
48 ms
pe.gif
43 ms
ph.gif
49 ms
pt.gif
58 ms
ro.gif
67 ms
ru.gif
65 ms
sa.gif
49 ms
sg.gif
50 ms
za.gif
51 ms
es.gif
63 ms
se.gif
69 ms
ch.gif
70 ms
th.gif
43 ms
tr.gif
53 ms
tw.gif
45 ms
uk.gif
57 ms
uae.gif
63 ms
us.gif
61 ms
vn.gif
47 ms
sensodyne.com.ar 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
sensodyne.com.ar 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
sensodyne.com.ar SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sensodyne.com.ar can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Sensodyne.com.ar 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.
sensodyne.com.ar
Open Graph description is not detected on the main page of Sensodyne. 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: