Tools & Wizards About Us
chiefence.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

chiefence.com

Metal Fence, Fencing Supplies, Electric Fence For Garden, Wire Fence Manufacturer

Page Load Speed

6.2 sec in total

First Response

358 ms

Resources Loaded

5.3 sec

Page Rendered

543 ms

chiefence.com screenshot

About Website

Click here to check amazing Chie Fence content. Otherwise, check out these important facts you probably never knew about chiefence.com

Fencing Supplies - Hebei Loni Chiefence Metal Product Co. Ltd is one of the leading metal fence, fencing supplies, electric fence for garden, wire fence manufacturer and supplier company in China. For...

Visit chiefence.com

Key Findings

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

chiefence.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value1,250 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.322

36/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

chiefence.com

358 ms

www.chiefence.com

593 ms

js

65 ms

js

121 ms

main.css

217 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 73% of them (67 requests) were addressed to the original Chiefence.com, 24% (22 requests) were made to Chat.chukouplus.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Chiefence.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.9 kB (7%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 62.1 kB

  • Original 76.4 kB
  • After minification 65.5 kB
  • After compression 14.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 10.9 kB, which is 14% 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 62.1 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 5.8 kB

  • Original 1.4 MB
  • After minification 1.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. Chie Fence images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 43.3 kB

  • Original 173.7 kB
  • After minification 173.7 kB
  • After compression 130.4 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 43.3 kB or 25% of the original size.

CSS Optimization

-8%

Potential reduce by 2.7 kB

  • Original 35.2 kB
  • After minification 35.2 kB
  • After compression 32.4 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. Chiefence.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (46%)

Requests Now

83

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chiefence.com

chiefence.com

358 ms

www.chiefence.com

www.chiefence.com

593 ms

js

js

65 ms

js

js

121 ms

main.css

main.css

217 ms

jquery.js

jquery.js

305 ms

slick.min.js

slick.min.js

243 ms

js-sdk-pro.min.js

js-sdk-pro.min.js

1185 ms

placeholder.js

placeholder.js

178 ms

resize.js

resize.js

200 ms

baguetteBox.js

baguetteBox.js

205 ms

slide.js

slide.js

224 ms

sm.js

sm.js

306 ms

flqiehuan.js

flqiehuan.js

307 ms

qiehuan.js

qiehuan.js

307 ms

base.js

base.js

307 ms

form1.js

form1.js

308 ms

lang.png

lang.png

284 ms

5ee41f73c1f6a.png

5ee41f73c1f6a.png

272 ms

logo.png

logo.png

71 ms

6333c62fd8475.jpg

6333c62fd8475.jpg

470 ms

6333dca1add18.jpg

6333dca1add18.jpg

612 ms

6333dd1d2e1ad.jpg

6333dd1d2e1ad.jpg

403 ms

6333dd4862d92.jpg

6333dd4862d92.jpg

489 ms

jt.png

jt.png

350 ms

ai1.png

ai1.png

358 ms

ai2.png

ai2.png

419 ms

ai3.png

ai3.png

426 ms

ai4.png

ai4.png

469 ms

ai5.png

ai5.png

488 ms

ai6.png

ai6.png

492 ms

5ef7f060980ec.jpg

5ef7f060980ec.jpg

553 ms

sypcover.png

sypcover.png

535 ms

5efab8094eb7c.jpg

5efab8094eb7c.jpg

647 ms

5ef7f0e8d7722.jpg

5ef7f0e8d7722.jpg

564 ms

5ef7f12627a48.jpg

5ef7f12627a48.jpg

626 ms

5ef7f166960fb.jpg

5ef7f166960fb.jpg

599 ms

5ef7fa2ee9c12.jpg

5ef7fa2ee9c12.jpg

619 ms

5ef7fa634e657.jpg

5ef7fa634e657.jpg

635 ms

5ef7faa68aace.jpg

5ef7faa68aace.jpg

665 ms

bg1.jpg

bg1.jpg

677 ms

wen.png

wen.png

685 ms

wi1.png

wi1.png

693 ms

wi2.png

wi2.png

704 ms

wi3.png

wi3.png

715 ms

sybg1.png

sybg1.png

731 ms

web1.png

web1.png

744 ms

bf1.png

bf1.png

714 ms

syzs.jpg

syzs.jpg

865 ms

syn.jpg

syn.jpg

735 ms

lxtu.jpg

lxtu.jpg

744 ms

index.php

index.php

1026 ms

iconfont.woff

iconfont.woff

838 ms

iconfont.eot

iconfont.eot

776 ms

AkzidenzGrotesk-ExtraBoldAlt.woff

AkzidenzGrotesk-ExtraBoldAlt.woff

602 ms

AkzidenzGrotesk-ExtraBoldAlt.woff

AkzidenzGrotesk-ExtraBoldAlt.woff

573 ms

AkzidenzGrotesk-Bold.woff

AkzidenzGrotesk-Bold.woff

562 ms

wx.png

wx.png

587 ms

reanod.png

reanod.png

543 ms

sybg2.png

sybg2.png

527 ms

yinying.png

yinying.png

563 ms

syzscover.png

syzscover.png

520 ms

synxian.png

synxian.png

525 ms

xing.jpg

xing.jpg

522 ms

error_html

error_html

1919 ms

error_html

error_html

1902 ms

init_kefu.js

init_kefu.js

1075 ms

kefu-logo.png

kefu-logo.png

212 ms

init_kefu.css

init_kefu.css

423 ms

index

index

716 ms

open.png

open.png

212 ms

kefu-logo2.png

kefu-logo2.png

230 ms

mobile-close.png

mobile-close.png

423 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

456 ms

index.js

index.js

212 ms

webuploader.css

webuploader.css

336 ms

kefu_chat.css

kefu_chat.css

347 ms

placeholder.js

placeholder.js

423 ms

kefu_chat.js

kefu_chat.js

542 ms

jqurey-form.js

jqurey-form.js

770 ms

webuploader.js

webuploader.js

1060 ms

upload.js

upload.js

653 ms

upload2.js

upload2.js

688 ms

layer.js

layer.js

749 ms

AkzidenzGrotesk-ExtraBoldAlt.ttf

AkzidenzGrotesk-ExtraBoldAlt.ttf

67 ms

error_html

error_html

243 ms

AkzidenzGrotesk-ExtraBoldAlt.svg

AkzidenzGrotesk-ExtraBoldAlt.svg

67 ms

error_html

error_html

131 ms

file-img.png

file-img.png

393 ms

fine-file.png

fine-file.png

434 ms

commit.png

commit.png

478 ms

layer.css

layer.css

213 ms

Accessibility Review

chiefence.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-*] 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

chiefence.com SEO score

83

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chiefence.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 Chiefence.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

chiefence.com

Open Graph data is detected on the main page of Chie Fence. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: