Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

inside.unilever.com

Something went wrong

Page Load Speed

2.1 sec in total

First Response

179 ms

Resources Loaded

1.8 sec

Page Rendered

139 ms

inside.unilever.com screenshot

About Website

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

Visit inside.unilever.com

Key Findings

We analyzed Inside.unilever.com page load time and found that the first response time was 179 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

inside.unilever.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

authorize

179 ms

login_ltr.min.css

171 ms

jquery-1.11.2.min.js

244 ms

jquery-migrate-1.2.1.min.js

218 ms

jquery.easing.1.3.js

234 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Inside.unilever.com, 11% (1 request) were made to Login.microsoftonline.com. The less responsive or slowest element that took the longest time to load (299 ms) relates to the external source Secure.aadcdn.microsoftonline-p.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 262.1 kB (31%)

Content Size

857.9 kB

After Optimization

595.8 kB

In fact, the total size of Inside.unilever.com main page is 857.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. 15% of websites need less resources to load. Images take 526.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 30.0 kB

  • Original 38.3 kB
  • After minification 33.6 kB
  • After compression 8.3 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.6 kB, which is 12% 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 30.0 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 16.3 kB

  • Original 526.1 kB
  • After minification 509.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. Inside Unilever images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 198.7 kB

  • Original 271.7 kB
  • After minification 269.3 kB
  • After compression 73.0 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 198.7 kB or 73% of the original size.

CSS Optimization

-79%

Potential reduce by 17.1 kB

  • Original 21.8 kB
  • After minification 21.5 kB
  • After compression 4.7 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. Inside.unilever.com needs all CSS files to be minified and compressed as it can save up to 17.1 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (38%)

Requests Now

8

After Optimization

5

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

Accessibility Review

inside.unilever.com accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

inside.unilever.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

inside.unilever.com SEO score

92

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inside.unilever.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Inside.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

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