Tools & Wizards About Us
autopartz.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

autopartz.com

Auto Parts Find | Car Parts Prices Online | AutoPartz Nigeria

Page Load Speed

2.1 sec in total

First Response

143 ms

Resources Loaded

1.7 sec

Page Rendered

337 ms

autopartz.com screenshot

About Website

Welcome to autopartz.com homepage info - get ready to check Auto Partz best content for Nigeria right away, or after learning these important things about autopartz.com

AutoPartz Nigeria; Find Car Spare Parts Costs (New or Used) with Suppliers; and Prices of Auto Mechanics, Electricians Services Online.

Visit autopartz.com

Key Findings

We analyzed Autopartz.com page load time and found that the first response time was 143 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 40% of websites can load faster.

Performance Metrics

autopartz.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.559

13/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

autopartz.com

143 ms

www.autopartz.com

543 ms

facebox.css

106 ms

style.css

161 ms

jquery-1.11.3.min.js

48 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 81% of them (68 requests) were addressed to the original Autopartz.com, 5% (4 requests) were made to Code.jquery.com and 2% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (617 ms) belongs to the original domain Autopartz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 640.8 kB (15%)

Content Size

4.2 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-90%

Potential reduce by 366.2 kB

  • Original 408.5 kB
  • After minification 342.3 kB
  • After compression 42.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 66.2 kB, which is 16% 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 366.2 kB or 90% of the original size.

Image Optimization

-7%

Potential reduce by 247.2 kB

  • Original 3.6 MB
  • After minification 3.4 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. Auto Partz images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 24.0 kB

  • Original 169.5 kB
  • After minification 169.4 kB
  • After compression 145.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 24.0 kB or 14% of the original size.

CSS Optimization

-13%

Potential reduce by 3.3 kB

  • Original 26.1 kB
  • After minification 26.1 kB
  • After compression 22.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. Autopartz.com needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (62%)

Requests Now

77

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

autopartz.com

autopartz.com

143 ms

www.autopartz.com

www.autopartz.com

543 ms

facebox.css

facebox.css

106 ms

style.css

style.css

161 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

48 ms

jquery.bxSlider.min.js

jquery.bxSlider.min.js

175 ms

facebox.js

facebox.js

175 ms

custom.js

custom.js

216 ms

geoip2.js

geoip2.js

58 ms

js

js

96 ms

element.js

element.js

74 ms

font-awesome.css

font-awesome.css

174 ms

menu-vertical.css

menu-vertical.css

159 ms

jquery-ui.css

jquery-ui.css

7 ms

jquery-ui.js

jquery-ui.js

9 ms

jshashtable-2.1_src.js

jshashtable-2.1_src.js

162 ms

jquery.numberformatter-1.2.3.js

jquery.numberformatter-1.2.3.js

163 ms

tmpl.js

tmpl.js

246 ms

jquery.dependClass-0.1.js

jquery.dependClass-0.1.js

162 ms

draggable-0.1.js

draggable-0.1.js

162 ms

jquery.slider.js

jquery.slider.js

273 ms

css-stars.css

css-stars.css

274 ms

jquery.barrating.js

jquery.barrating.js

273 ms

examples.js

examples.js

274 ms

jquery.validate.js

jquery.validate.js

273 ms

ajax-autocomplete.js

ajax-autocomplete.js

274 ms

ajax-autocomplete.css

ajax-autocomplete.css

314 ms

me

me

141 ms

all.js

all.js

140 ms

bg.png

bg.png

90 ms

homeicon.png

homeicon.png

95 ms

icon.png

icon.png

96 ms

usericon.png

usericon.png

95 ms

loginicon.png

loginicon.png

90 ms

lanicon.png

lanicon.png

154 ms

logo.png

logo.png

200 ms

editpencil.png

editpencil.png

157 ms

searchico1.png

searchico1.png

156 ms

searchicon.png

searchicon.png

156 ms

searchico2.png

searchico2.png

157 ms

e1bdb61041185ffee6464b1d3157d3aa.jpg

e1bdb61041185ffee6464b1d3157d3aa.jpg

247 ms

categoryicon.png

categoryicon.png

202 ms

59552_Slider%201d%20-.jpg

59552_Slider%201d%20-.jpg

463 ms

36483_Slider%202c%20-.jpg

36483_Slider%202c%20-.jpg

462 ms

86541_Slider%203d%20-.jpeg

86541_Slider%203d%20-.jpeg

617 ms

27962_KYB%20Shocks%20Modified.jpeg

27962_KYB%20Shocks%20Modified.jpeg

305 ms

68dccc7324c3d95cdbcea81710d37f3e.jpeg

68dccc7324c3d95cdbcea81710d37f3e.jpeg

256 ms

b3a0e937d2868c3e10826ee625de51a4.jpeg

b3a0e937d2868c3e10826ee625de51a4.jpeg

303 ms

e38b600e4540f63c3daa6c9a1c283591.jpeg

e38b600e4540f63c3daa6c9a1c283591.jpeg

310 ms

957b8093e9d13a163c45a165cb468943.jpeg

957b8093e9d13a163c45a165cb468943.jpeg

354 ms

63538d82980e882d3ceee803e3d0b6db.jpeg

63538d82980e882d3ceee803e3d0b6db.jpeg

359 ms

7146d8777129afe928756c68fccd4bde.jpeg

7146d8777129afe928756c68fccd4bde.jpeg

364 ms

arrpw.jpg.gif

arrpw.jpg.gif

408 ms

no-image-icon1.jpg

no-image-icon1.jpg

412 ms

50c70738639d5421051727d8d715839c.jpg

50c70738639d5421051727d8d715839c.jpg

470 ms

b99df60305a43686258cc046db17c7c6.jpg

b99df60305a43686258cc046db17c7c6.jpg

514 ms

closelabel.png

closelabel.png

448 ms

bebasneue1.woff

bebasneue1.woff

494 ms

helveticalt.woff

helveticalt.woff

466 ms

64094_images%20(1).jpeg

64094_images%20(1).jpeg

470 ms

comment_transparent.png

comment_transparent.png

477 ms

face.png

face.png

518 ms

tweet.png

tweet.png

516 ms

analytics.js

analytics.js

75 ms

pintrest.png

pintrest.png

487 ms

all.js

all.js

46 ms

winicon.png

winicon.png

533 ms

bblockbg.png

bblockbg.png

533 ms

fotertopbg.png

fotertopbg.png

531 ms

v2.zopim.com

v2.zopim.com

81 ms

closelabel.png

closelabel.png

92 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

22 ms

footlinkbg.png

footlinkbg.png

537 ms

107 ms

footlisticon.png

footlisticon.png

526 ms

pagingbg.png

pagingbg.png

527 ms

closelabel.png

closelabel.png

529 ms

loading.gif

loading.gif

572 ms

collect

collect

16 ms

footprev.png

footprev.png

567 ms

asset_composer.js

asset_composer.js

31 ms

footnext.png

footnext.png

539 ms

calendar.gif

calendar.gif

538 ms

selectedbanner.png

selectedbanner.png

280 ms

Accessibility Review

autopartz.com accessibility score

66

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

autopartz.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

autopartz.com SEO score

73

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

autopartz.com

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