Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

milliken.com

Milliken & Company, A Global Manufacturing Leader | Milliken

Page Load Speed

7.1 sec in total

First Response

150 ms

Resources Loaded

4.1 sec

Page Rendered

2.8 sec

About Website

Click here to check amazing Milliken content for India. Otherwise, check out these important facts you probably never knew about milliken.com

Milliken a leading manufacturing companies specializing in flooring, textiles, chemicals & healthcare solutions. Explore our innovative solutions now!

Visit milliken.com

Key Findings

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

Performance Metrics

milliken.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value3,740 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

milliken.com

150 ms

www.milliken.com

398 ms

146 ms

gtm.js

164 ms

style.min.css

163 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 65% of them (50 requests) were addressed to the original Milliken.com, 6% (5 requests) were made to Cdnjs.cloudflare.com and 5% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Milliken.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 180.7 kB (21%)

Content Size

880.4 kB

After Optimization

699.8 kB

In fact, the total size of Milliken.com main page is 880.4 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. 85% 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 577.5 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 142.8 kB

  • Original 161.4 kB
  • After minification 102.5 kB
  • After compression 18.6 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 58.9 kB, which is 37% 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 142.8 kB or 88% of the original size.

Image Optimization

-6%

Potential reduce by 34.8 kB

  • Original 577.5 kB
  • After minification 542.8 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. Milliken images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 3.1 kB

  • Original 75.8 kB
  • After minification 75.7 kB
  • After compression 72.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 65.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.

Requests Breakdown

Number of requests can be reduced by 35 (59%)

Requests Now

59

After Optimization

24

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Milliken. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

milliken.com accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not have valid values

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

milliken.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

milliken.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

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 Milliken.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 Milliken.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 data is detected on the main page of Milliken. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: