Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

worthyparts.com

Worthy Parts | Heavy Parts, Machinery, Components & Equipment

Page Load Speed

7.5 sec in total

First Response

995 ms

Resources Loaded

4.2 sec

Page Rendered

2.2 sec

About Website

Click here to check amazing Worthy Parts content for Australia. Otherwise, check out these important facts you probably never knew about worthyparts.com

At Worthy Parts we provide you with the best way to buy & sell Heavy Underground Parts, Machinery, Components & Earthmoving Equipment

Visit worthyparts.com

Key Findings

We analyzed Worthyparts.com page load time and found that the first response time was 995 ms and then it took 6.5 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

worthyparts.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value3,440 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value30.2 s

0/100

10%

Network Requests Diagram

www.worthyparts.com

995 ms

style.min.css

31 ms

styles.css

26 ms

gui_main.css

244 ms

sfsi-style.css

27 ms

Our browser made a total of 162 requests to load all elements on the main page. We found that 84% of them (136 requests) were addressed to the original Worthyparts.com, 6% (9 requests) were made to Fonts.gstatic.com and 2% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Worthyparts.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 246.3 kB (4%)

Content Size

6.9 MB

After Optimization

6.7 MB

In fact, the total size of Worthyparts.com main page is 6.9 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 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 189.2 kB

  • Original 233.4 kB
  • After minification 193.6 kB
  • After compression 44.1 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 39.7 kB, which is 17% 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 189.2 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 6.0 MB
  • After minification 6.0 MB

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. Worthy Parts images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 16.8 kB

  • Original 537.7 kB
  • After minification 537.7 kB
  • After compression 520.9 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

-32%

Potential reduce by 40.2 kB

  • Original 127.0 kB
  • After minification 94.7 kB
  • After compression 86.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. Worthyparts.com needs all CSS files to be minified and compressed as it can save up to 40.2 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 82 (54%)

Requests Now

152

After Optimization

70

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

Accessibility Review

worthyparts.com accessibility score

57

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 match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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.

High

[aria-*] attributes do not have valid values

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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.

Best Practices

worthyparts.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

worthyparts.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

High

Tap targets are not sized appropriately

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 Worthyparts.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 Worthyparts.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 Worthy Parts. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: