Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 0

    Best Practices

  • 74

    SEO

    Google-friendlier than
    32% of websites

trw.com

TRW Automotive Aftermarket | Auto Car Parts

Page Load Speed

13.1 sec in total

First Response

606 ms

Resources Loaded

5.7 sec

Page Rendered

6.8 sec

trw.com screenshot

About Website

Welcome to trw.com homepage info - get ready to check TRW best content for India right away, or after learning these important things about trw.com

TRW Aftermarket - a global leader in auto parts for the aftermarket. Premium quality car parts for maximum safety.

Visit trw.com

Key Findings

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

Performance Metrics

trw.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value45.3 s

0/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value2,200 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.164

72/100

15%

TTI (Time to Interactive)

Value44.7 s

0/100

10%

Network Requests Diagram

trw.com

606 ms

309 ms

454 ms

1465 ms

style.css

633 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 11% of them (1 request) were addressed to the original Trw.com, 67% (6 requests) were made to Zf.com and 22% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Zf.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 759.5 kB (43%)

Content Size

1.8 MB

After Optimization

1.0 MB

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

HTML Optimization

-73%

Potential reduce by 5.2 kB

  • Original 7.1 kB
  • After minification 6.7 kB
  • After compression 1.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 5.2 kB or 73% of the original size.

Image Optimization

-15%

Potential reduce by 151.2 kB

  • Original 1.0 MB
  • After minification 862.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, TRW needs image optimization as it can save up to 151.2 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-76%

Potential reduce by 419.4 kB

  • Original 552.9 kB
  • After minification 403.2 kB
  • After compression 133.5 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 419.4 kB or 76% of the original size.

CSS Optimization

-87%

Potential reduce by 183.7 kB

  • Original 211.5 kB
  • After minification 155.8 kB
  • After compression 27.8 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. Trw.com needs all CSS files to be minified and compressed as it can save up to 183.7 kB or 87% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TRW. According to our analytics all requests are already optimized.

Accessibility Review

trw.com accessibility score

61

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

SEO Factors

trw.com SEO score

74

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

High

Tap targets are not sized appropriately

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 Trw.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 Trw.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 TRW. 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: