3.3 sec in total
168 ms
2.3 sec
830 ms
Welcome to oldspice.in homepage info - get ready to check Oldspice best content for India right away, or after learning these important things about oldspice.in
Old Spice has 75 years of experience helping guys improve their mansmells with deodorant, antiperspirant and fragrances. Come on in to find out more.
Visit oldspice.inWe analyzed Oldspice.in page load time and found that the first response time was 168 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
oldspice.in performance score
168 ms
386 ms
256 ms
361 ms
192 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 7% of them (5 requests) were addressed to the original Oldspice.in, 68% (50 requests) were made to Cdn.titan.pgsitecore.com and 8% (6 requests) were made to S.btstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Cdn.titan.pgsitecore.com.
Page size can be reduced by 961.9 kB (18%)
5.4 MB
4.5 MB
In fact, the total size of Oldspice.in main page is 5.4 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 5.2 MB which makes up the majority of the site volume.
Potential reduce by 58.8 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 17.3 kB, which is 24% 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 58.8 kB or 82% of the original size.
Potential reduce by 813.6 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, Oldspice needs image optimization as it can save up to 813.6 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 89.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 89.4 kB or 66% of the original size.
Number of requests can be reduced by 34 (50%)
68
34
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oldspice. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
oldspice.in
168 ms
386 ms
globalltr
256 ms
sitemaster
361 ms
sitelocale
192 ms
WebResource.axd
97 ms
ScriptResource.axd
189 ms
ScriptResource.axd
153 ms
commonscript
97 ms
adblock.js
88 ms
desktop
353 ms
siteroot
279 ms
tag.js
79 ms
async-ads.js
108 ms
OS_DESKTOP_BG.png
1388 ms
Rewardme_Logo_CC.png
74 ms
DT_PGFamily-03.png
78 ms
DT_PGFamily-04.png
80 ms
ModalDialogClose.png
92 ms
South_Africa.png
89 ms
india-1.png
93 ms
Hungary.png
91 ms
Poland.png
94 ms
Russia.png
94 ms
Brazil.png
93 ms
Colombia.png
96 ms
Mexico.png
95 ms
Canada_eng.png
96 ms
Canada_French.png
97 ms
USA.png
96 ms
DT_Logo_White.png
99 ms
SearchBoxImage.png
97 ms
Products_900x900_BODY_SPRAY_SWAGGER_BS.jpg
336 ms
Products_900x900_FRAGRANCE_CLASSIC_COLOGNE.jpg
330 ms
970x420-a.jpg
208 ms
970x420-b.jpg
220 ms
Banner%202b.jpg
206 ms
Banner%201.jpg
208 ms
Banner%203a.jpg
330 ms
SP_Social_Facebook_72x72.png
217 ms
DT_Social_Twitter_34x34.png
330 ms
DT_Social_YouTube_34x34.png
331 ms
ad%20choice.png
331 ms
DT_Bkgrd_Header_bg.jpg
269 ms
country_selector_BG_new.jpg
273 ms
top-menu_arrow.png
269 ms
Sub_menu_bg_new1.png
276 ms
sub_menu_2.jpg
561 ms
carousel-pic.jpg
270 ms
page_2on.png
272 ms
page_2off.png
358 ms
arrow_left.png
359 ms
arrowright.png
348 ms
DT_Bkgrd_Tiles_Paper-Medium_new.jpg
350 ms
SP_Bkgrd_Tiles_Blue-ProductDetails-HeroArea_new.jpg
407 ms
iframe_api
111 ms
tag
105 ms
cdn.titan.pgsitecore.com
52 ms
www-widgetapi.js
87 ms
76708d84f7e7a4b4b1a779b1d0afcd7997af4e20.js
40 ms
en
74 ms
76e5c2ebb0ce721688b62332fceb2206ef45fc84.js
47 ms
a46f12f820f911feb7336318592d831fdc200db9.js
42 ms
278afe2d73add98b2852b30170b81e0cd7f64e79.js
45 ms
fb3d4287e244e2ecd6aa1fa7c860158ec05ba7ac.js
62 ms
tag
84 ms
gw.js
234 ms
analytics.js
113 ms
collect
60 ms
collect
87 ms
collect
71 ms
collect
208 ms
45969666.js
124 ms
oldspice.in SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oldspice.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Oldspice.in 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.
oldspice.in
Open Graph description is not detected on the main page of Oldspice. 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: