Tools & Wizards About Us
pu-kang.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

pu-kang.com

Insulin Degludec Side Chain, Semaglutide Side Chain Manufacturer - Pukang

Page Load Speed

6.3 sec in total

First Response

253 ms

Resources Loaded

3 sec

Page Rendered

3.1 sec

pu-kang.com screenshot

About Website

Welcome to pu-kang.com homepage info - get ready to check Pukang best content right away, or after learning these important things about pu-kang.com

We are a professional chemical supplier of high purity single molecular PEG series derivatives polypeptide long acting drug side chain and its intermediates. If you are looking for a trusted partner, ...

Visit pu-kang.com

Key Findings

We analyzed Pu-kang.com page load time and found that the first response time was 253 ms and then it took 6 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

pu-kang.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.081

94/100

15%

TTI (Time to Interactive)

Value25.9 s

0/100

10%

Network Requests Diagram

www.pu-kang.com

253 ms

picture.description.css

39 ms

jumpNum.css

52 ms

button.css

62 ms

style.css

60 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Pu-kang.com, 50% (32 requests) were made to Inrorwxhjkmllo5p.leadongcdn.com and 20% (13 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Inrorwxhjkmllo5p.leadongcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 861.7 kB (3%)

Content Size

30.9 MB

After Optimization

30.0 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-86%

Potential reduce by 339.0 kB

  • Original 394.0 kB
  • After minification 394.0 kB
  • After compression 55.0 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 339.0 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 498.8 kB

  • Original 30.3 MB
  • After minification 29.8 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. Pukang images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 23.9 kB

  • Original 188.4 kB
  • After minification 188.4 kB
  • After compression 164.6 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 23.9 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (35%)

Requests Now

60

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.pu-kang.com

www.pu-kang.com

253 ms

picture.description.css

picture.description.css

39 ms

jumpNum.css

jumpNum.css

52 ms

button.css

button.css

62 ms

style.css

style.css

60 ms

rrkkKBmjrkRlkSljomRliSjorjqpRliSjljoikRljSjrrlrkiklrjrRpiSrqlmkkjorprrSRil.css

rrkkKBmjrkRlkSljomRliSjorjqpRliSjljoikRljSjrrlrkiklrjrRpiSrqlmkkjorprrSRil.css

29 ms

js

js

50 ms

speedLazyLoad4.min.js

speedLazyLoad4.min.js

27 ms

bat.js

bat.js

87 ms

yetoubj.jpg

yetoubj.jpg

126 ms

1ogo.png

1ogo.png

126 ms

captcha

captcha

547 ms

1fglgluv3

1fglgluv3

48 ms

0.jpg

0.jpg

33 ms

d8ce1f87-121d-4a8d-bee2-f53a346b7a6e.jpg

d8ce1f87-121d-4a8d-bee2-f53a346b7a6e.jpg

234 ms

2.jpg

2.jpg

186 ms

banner02.png

banner02.png

282 ms

banner03-kaobei.png

banner03-kaobei.png

226 ms

crop_1651127721004.png

crop_1651127721004.png

194 ms

about.jpg

about.jpg

234 ms

icon1.png

icon1.png

315 ms

icon2.png

icon2.png

291 ms

icon3.png

icon3.png

371 ms

icon4.png

icon4.png

357 ms

shu.jpg

shu.jpg

401 ms

crop_1681265450488.png

crop_1681265450488.png

637 ms

IMG_5683.jpg

IMG_5683.jpg

726 ms

13.jpg

13.jpg

807 ms

crop_1651200077797.png

crop_1651200077797.png

476 ms

ADC-300-300.png

ADC-300-300.png

641 ms

qiyeweixinjietu_16354300337616-300-300.png

qiyeweixinjietu_16354300337616-300-300.png

600 ms

PROTAC-300-300.jpg

PROTAC-300-300.jpg

634 ms

22.png

22.png

712 ms

icon5.png

icon5.png

746 ms

icon6.png

icon6.png

1173 ms

icon7.png

icon7.png

869 ms

icon8.png

icon8.png

863 ms

icon9.png

icon9.png

853 ms

icon10.png

icon10.png

907 ms

follow-ser.png

follow-ser.png

906 ms

0.jpg

0.jpg

24 ms

d8ce1f87-121d-4a8d-bee2-f53a346b7a6e.jpg

d8ce1f87-121d-4a8d-bee2-f53a346b7a6e.jpg

230 ms

aboutbj.jpg

aboutbj.jpg

188 ms

22.jpg

22.jpg

132 ms

11.jpg

11.jpg

188 ms

yejiao-bj.jpg

yejiao-bj.jpg

229 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

896 ms

148005050.js

148005050.js

11 ms

148005050

148005050

1092 ms

iconfont.woff

iconfont.woff

787 ms

clarity.js

clarity.js

14 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

30 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

57 ms

twk-event-polyfill.js

twk-event-polyfill.js

171 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

16 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

58 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

209 ms

twk-main.js

twk-main.js

88 ms

twk-vendor.js

twk-vendor.js

41 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

76 ms

twk-chunk-common.js

twk-chunk-common.js

68 ms

twk-runtime.js

twk-runtime.js

68 ms

twk-app.js

twk-app.js

87 ms

c.gif

c.gif

11 ms

Accessibility Review

pu-kang.com accessibility score

80

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.

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

Links do not have a discernible name

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

pu-kang.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

pu-kang.com SEO score

93

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

    EN

  • Encoding

    UTF-8

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

pu-kang.com

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