Tools & Wizards About Us
wiper-blade.net screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

wiper-blade.net

Custom Car Wiper Manufacturers, Auto Wiper Blades Factory

Page Load Speed

5.5 sec in total

First Response

617 ms

Resources Loaded

3.9 sec

Page Rendered

1 sec

wiper-blade.net screenshot

About Website

Welcome to wiper-blade.net homepage info - get ready to check Wiper Blade best content right away, or after learning these important things about wiper-blade.net

Ningbo Zhenhai Jinjian Autoparts Limited Company is China Car Wiper Blades Manufacturers and Custom Auto Wiper Blades Factory, offer Car Auto Wiper Blades for sale.

Visit wiper-blade.net

Key Findings

We analyzed Wiper-blade.net page load time and found that the first response time was 617 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

wiper-blade.net performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value1,730 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value1.053

2/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

www.wiper-blade.net

617 ms

156 ms

171 ms

analyze.js

837 ms

index_js.js

105 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 88% of them (57 requests) were addressed to the original Wiper-blade.net, 5% (3 requests) were made to Rt.xiaoman.cn and 2% (1 request) were made to Tfile.xiaoman.cn. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Supertest.hqsmartcloud.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 49.1 kB (5%)

Content Size

912.2 kB

After Optimization

863.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wiper-blade.net main page is 912.2 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. 60% of websites need less resources to load. Images take 789.9 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 46.5 kB

  • Original 54.1 kB
  • After minification 40.8 kB
  • After compression 7.7 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 13.3 kB, which is 25% 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 46.5 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 2.3 kB

  • Original 789.9 kB
  • After minification 787.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. Wiper Blade images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 291 B

  • Original 68.1 kB
  • After minification 68.1 kB
  • After compression 67.8 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.

Requests Breakdown

Number of requests can be reduced by 16 (34%)

Requests Now

47

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wiper-blade.net

www.wiper-blade.net

617 ms

156 ms

171 ms

analyze.js

analyze.js

837 ms

index_js.js

index_js.js

105 ms

layer.js

layer.js

84 ms

email-decode.min.js

email-decode.min.js

13 ms

matomo.js

matomo.js

742 ms

logo.png

logo.png

123 ms

icon-search.png

icon-search.png

123 ms

banner-mask.png

banner-mask.png

133 ms

banner.jpg

banner.jpg

222 ms

init-1-bg.jpg

init-1-bg.jpg

169 ms

logo-white.png

logo-white.png

123 ms

init-1-1-bg.jpg

init-1-1-bg.jpg

190 ms

universal-wiper-blade.png

universal-wiper-blade.png

550 ms

multifunction-wiper-blade-1.png

multifunction-wiper-blade-1.png

548 ms

hybrid-wiper-blade.png

hybrid-wiper-blade.png

673 ms

winter-wiper-blade.png

winter-wiper-blade.png

326 ms

rear-wiper-blade.png

rear-wiper-blade.png

580 ms

bus-&-truck-wiper-blade.png

bus-&-truck-wiper-blade.png

671 ms

wiper-blade-for-iran-market.png

wiper-blade-for-iran-market.png

736 ms

special-wiper-blade.png

special-wiper-blade.png

735 ms

wiper-relative-products-2.png

wiper-relative-products-2.png

1252 ms

c.jpg

c.jpg

1000 ms

init-2-bg.jpg

init-2-bg.jpg

707 ms

h726eca0dbb29400fb18db6222f281f18p.jpg

h726eca0dbb29400fb18db6222f281f18p.jpg

840 ms

htb1gaavfh1ybunjsszeq6yblfxav.jpg

htb1gaavfh1ybunjsszeq6yblfxav.jpg

816 ms

htb1jrh3lqumbknjszfoq6yb2xxa7.jpg

htb1jrh3lqumbknjszfoq6yb2xxa7.jpg

909 ms

htb1e8ksg1ysbunjy1zdq6xpxfxan.jpg

htb1e8ksg1ysbunjy1zdq6xpxfxan.jpg

968 ms

htb1cmz.asfrk1rksnb4q6xhrfxaz.jpg

htb1cmz.asfrk1rksnb4q6xhrfxaz.jpg

939 ms

h2c79a21fa0424983be64523dc44d286an.jpg

h2c79a21fa0424983be64523dc44d286an.jpg

1001 ms

utb8ufocfbahdujk43jaq6zm8fxag.jpg

utb8ufocfbahdujk43jaq6zm8fxag.jpg

1057 ms

htb107comhznbknjszfhq6a.oxxav.jpg

htb107comhznbknjszfhq6a.oxxav.jpg

1039 ms

init-3-bg.jpg

init-3-bg.jpg

1086 ms

init-5-bg.jpg

init-5-bg.jpg

1074 ms

icon-5-1.png

icon-5-1.png

1093 ms

icon-5-2.png

icon-5-2.png

1097 ms

icon-5-3.png

icon-5-3.png

1155 ms

icon-5-4.png

icon-5-4.png

1138 ms

init-6-bg.jpg

init-6-bg.jpg

1177 ms

init-6-1.jpg

init-6-1.jpg

1186 ms

init-6-2.jpg

init-6-2.jpg

1163 ms

FuturaBT-Book.ttf

FuturaBT-Book.ttf

1233 ms

FuturaBT-Medium.ttf

FuturaBT-Medium.ttf

1165 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1132 ms

init-6-3.jpg

init-6-3.jpg

1188 ms

init-6-4.jpg

init-6-4.jpg

1157 ms

init-6-5.jpg

init-6-5.jpg

1143 ms

news_01.jpg

news_01.jpg

1564 ms

suangjiao2.png

suangjiao2.png

1599 ms

htb1ow68ayzxk1rksnavq6xn9vxao.jpg

htb1ow68ayzxk1rksnavq6xn9vxao.jpg

1091 ms

htb1agbulhznbknjszfkq6agovxau.jpg

htb1agbulhznbknjszfkq6agovxau.jpg

896 ms

icon-send.png

icon-send.png

821 ms

icon-mobile.png

icon-mobile.png

781 ms

siteSetting

siteSetting

1131 ms

icon-tel.png

icon-tel.png

770 ms

icon-mail.png

icon-mail.png

788 ms

icon-add.png

icon-add.png

816 ms

Technical-Support.svg

Technical-Support.svg

774 ms

matomo.php

matomo.php

1904 ms

js

js

66 ms

okki-chat-widget-sdk.iife.js

okki-chat-widget-sdk.iife.js

260 ms

report

report

318 ms

report

report

303 ms

Accessibility Review

wiper-blade.net accessibility score

85

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

wiper-blade.net 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

Missing source maps for large first-party JavaScript

SEO Factors

wiper-blade.net SEO score

92

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

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 Wiper-blade.net 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 Wiper-blade.net 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

wiper-blade.net

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