Tools & Wizards About Us
ccs.unilever.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ccs.unilever.com

User Log In

Page Load Speed

3.1 sec in total

First Response

360 ms

Resources Loaded

2.5 sec

Page Rendered

186 ms

ccs.unilever.com screenshot

About Website

Visit ccs.unilever.com now to see the best up-to-date Ccs Unilever content for India and also check out these interesting facts you probably never knew about ccs.unilever.com

Visit ccs.unilever.com

Key Findings

We analyzed Ccs.unilever.com page load time and found that the first response time was 360 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

ccs.unilever.com performance score

0

Network Requests Diagram

ccs.unilever.com

360 ms

395 ms

Default.aspx

436 ms

default.css

188 ms

skin.css

515 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that all of those requests were addressed to Ccs.unilever.com and no external sources were called. The less responsive or slowest element that took the longest time to load (819 ms) belongs to the original domain Ccs.unilever.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 631.8 kB (74%)

Content Size

855.7 kB

After Optimization

223.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ccs.unilever.com main page is 855.7 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. Javascripts take 674.3 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 20.6 kB

  • Original 29.1 kB
  • After minification 25.1 kB
  • After compression 8.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 4.0 kB, which is 14% 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 20.6 kB or 71% of the original size.

Image Optimization

-12%

Potential reduce by 11.3 kB

  • Original 93.3 kB
  • After minification 82.0 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, Ccs Unilever needs image optimization as it can save up to 11.3 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-82%

Potential reduce by 551.4 kB

  • Original 674.3 kB
  • After minification 528.2 kB
  • After compression 122.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 551.4 kB or 82% of the original size.

CSS Optimization

-82%

Potential reduce by 48.4 kB

  • Original 59.0 kB
  • After minification 47.8 kB
  • After compression 10.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. Ccs.unilever.com needs all CSS files to be minified and compressed as it can save up to 48.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (72%)

Requests Now

54

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ccs Unilever. 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 from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ccs.unilever.com

ccs.unilever.com

360 ms

395 ms

Default.aspx

Default.aspx

436 ms

default.css

default.css

188 ms

skin.css

skin.css

515 ms

index.css

index.css

272 ms

container.css

container.css

274 ms

Title_Grey.css

Title_Grey.css

275 ms

portal.css

portal.css

369 ms

jquery.js

jquery.js

365 ms

WebResource.axd

WebResource.axd

624 ms

dnncore.js

dnncore.js

453 ms

ScriptResource.axd

ScriptResource.axd

732 ms

ScriptResource.axd

ScriptResource.axd

455 ms

dnn.js

dnn.js

732 ms

dnn.xml.js

dnn.xml.js

541 ms

dnn.xmlhttp.js

dnn.xmlhttp.js

544 ms

dnn.dom.positioning.js

dnn.dom.positioning.js

599 ms

dnn.controls.js

dnn.controls.js

634 ms

dnn.controls.dnnmenu.js

dnn.controls.dnnmenu.js

636 ms

ScriptResource.axd

ScriptResource.axd

684 ms

ScriptResource.axd

ScriptResource.axd

709 ms

ScriptResource.axd

ScriptResource.axd

723 ms

ScriptResource.axd

ScriptResource.axd

723 ms

ScriptResource.axd

ScriptResource.axd

768 ms

ScriptResource.axd

ScriptResource.axd

797 ms

ScriptResource.axd

ScriptResource.axd

813 ms

ScriptResource.axd

ScriptResource.axd

811 ms

ScriptResource.axd

ScriptResource.axd

819 ms

initWidgets.js

initWidgets.js

819 ms

stylesheetwidget.css

stylesheetwidget.css

593 ms

menu.css

menu.css

385 ms

body_bg.png

body_bg.png

96 ms

en-US.gif

en-US.gif

98 ms

vi-VN.gif

vi-VN.gif

97 ms

th-TH.gif

th-TH.gif

95 ms

id-ID.gif

id-ID.gif

97 ms

en-PH.gif

en-PH.gif

88 ms

icon_authentication_32px.gif

icon_authentication_32px.gif

174 ms

cpanel_left.png

cpanel_left.png

140 ms

cpanel_right.png

cpanel_right.png

138 ms

ccs_header.jpg

ccs_header.jpg

141 ms

menu_left.gif

menu_left.gif

142 ms

menu_right.gif

menu_right.gif

143 ms

menu_bg.gif

menu_bg.gif

215 ms

bread_left.png

bread_left.png

226 ms

bread_right.png

bread_right.png

228 ms

bread_bg.jpg

bread_bg.jpg

230 ms

left_bg.png

left_bg.png

233 ms

right_bg.png

right_bg.png

234 ms

center_bg.jpg

center_bg.jpg

300 ms

dnn_headerItem.gif

dnn_headerItem.gif

317 ms

Login_bg.jpg

Login_bg.jpg

318 ms

dnn_button.gif

dnn_button.gif

320 ms

bot_left.png

bot_left.png

324 ms

bot_right.png

bot_right.png

326 ms

bot_bg.png

bot_bg.png

384 ms

SEO Factors

ccs.unilever.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ccs.unilever.com 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 Ccs.unilever.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.

Social Sharing Optimization

ccs.unilever.com

Open Graph description is not detected on the main page of Ccs Unilever. 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: