Tools & Wizards About Us
printhome.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

printhome.com

印刷家官网:专业印企服务平台,值得信赖！

Page Load Speed

30.7 sec in total

First Response

6.2 sec

Resources Loaded

24 sec

Page Rendered

471 ms

printhome.com screenshot

About Website

Visit printhome.com now to see the best up-to-date Printhome content and also check out these interesting facts you probably never knew about printhome.com

印刷家是一家垂直于印刷包装领域的全生态链服务平台。通过组织专业能力，赋能印企，创造印刷品新价值。八大版块驱动，赋能印企：咨询、工艺、金融、采购、推广、订单、系统、数据服务

Visit printhome.com

Key Findings

We analyzed Printhome.com page load time and found that the first response time was 6.2 sec and then it took 24.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

printhome.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value22.6 s

0/100

25%

SI (Speed Index)

Value19.5 s

0/100

10%

TBT (Total Blocking Time)

Value4,370 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

www.jcloud.com

6240 ms

gb.css

4474 ms

index.css

730 ms

placeholder@1x1_0868a4ac.png

747 ms

jcloud@1x_2e8f0f1e.png

729 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Printhome.com, 5% (1 request) were made to Wl.jd.com and 5% (1 request) were made to Mercury.jd.com. The less responsive or slowest element that took the longest time to load (6.3 sec) relates to the external source Jcloud.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 472.2 kB (28%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Printhome.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. 15% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 167.4 kB

  • Original 190.8 kB
  • After minification 128.3 kB
  • After compression 23.4 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 62.5 kB, which is 33% 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 167.4 kB or 88% of the original size.

Image Optimization

-20%

Potential reduce by 295.2 kB

  • Original 1.5 MB
  • After minification 1.2 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. Obviously, Printhome needs image optimization as it can save up to 295.2 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 9.5 kB

  • Original 15.9 kB
  • After minification 15.9 kB
  • After compression 6.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 9.5 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (18%)

Requests Now

17

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.jcloud.com

www.jcloud.com

6240 ms

gb.css

gb.css

4474 ms

index.css

index.css

730 ms

placeholder@1x1_0868a4ac.png

placeholder@1x1_0868a4ac.png

747 ms

jcloud@1x_2e8f0f1e.png

jcloud@1x_2e8f0f1e.png

729 ms

lib.js

lib.js

6285 ms

gb.js

gb.js

365 ms

index.min_7b030c45.js

index.min_7b030c45.js

350 ms

mod_hd_logo_@1x_41e260c0.png

mod_hd_logo_@1x_41e260c0.png

2056 ms

banner_loading@1x_cda802d0.gif

banner_loading@1x_cda802d0.gif

721 ms

user.png

user.png

348 ms

tel-btn.png

tel-btn.png

692 ms

fz_2333f699.woff

fz_2333f699.woff

1262 ms

iconfont_7ef5184a.woff

iconfont_7ef5184a.woff

1391 ms

joya.js

joya.js

366 ms

info

info

517 ms

jcloud_banner_2_@1x.png

jcloud_banner_2_@1x.png

3814 ms

log.gif

log.gif

1740 ms

info

info

1221 ms

jcloud_banner_1_@1x.png

jcloud_banner_1_@1x.png

6172 ms

Accessibility Review

printhome.com accessibility score

54

Accessibility Issues

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

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

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

printhome.com best practices score

58

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

printhome.com SEO score

75

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Printhome.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Printhome.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

printhome.com

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