7.8 sec in total
1.1 sec
5.5 sec
1.2 sec
Visit qcpt.org now to see the best up-to-date Qcpt content for China and also check out these interesting facts you probably never knew about qcpt.org
青创平台聚焦
Visit qcpt.orgWe analyzed Qcpt.org page load time and found that the first response time was 1.1 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
qcpt.org performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value23.1 s
0/100
25%
Value26.9 s
0/100
10%
Value7,000 ms
0/100
30%
Value0.003
100/100
15%
Value52.2 s
0/100
10%
1146 ms
1351 ms
991 ms
385 ms
338 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Qcpt.org, 75% (49 requests) were made to User-assets.sxlcdn.com and 14% (9 requests) were made to Static-assets.sxlcdn.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Static-fonts-css.sxlcdn.com.
Page size can be reduced by 1.7 MB (11%)
15.6 MB
13.9 MB
In fact, the total size of Qcpt.org main page is 15.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 15.2 MB which makes up the majority of the site volume.
Potential reduce by 266.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. 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 266.7 kB or 85% of the original size.
Potential reduce by 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. Qcpt images are well optimized though.
Potential reduce by 12 B
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.
Number of requests can be reduced by 4 (6%)
63
59
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qcpt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
qcpt.org
1146 ms
qcpt.org
1351 ms
show.js
991 ms
main_v4.141b5888d9c3cdadfb81.bundle.css
385 ms
detectIE-c385c24313ef0e9e4e7a1e131bf5e59f0fbd468f9f9ef44fd6739ae84ef0c0a4.js
338 ms
jquery.min.js
307 ms
i18n-2ace11ac644d0b40fb8b7cb65e9dd1e553022750e0254118dacbe1fe50735e97.js
133 ms
page-site-bundle.aa9bd820a56901669727.js
155 ms
FtJhUXtR-HrLe2RQVpnXBVwTSQnd.png
472 ms
power.png
260 ms
gongan-beian.png
258 ms
css
1787 ms
FqvH0S0OsCka5FUDbCNzOqn6poVv.png
482 ms
FpNpumvD-4kl7kMxgKTU1Ri2VEH6.png
485 ms
FiZzEh9RlG_uQcEQpZH4-qBshs3J.png
504 ms
FpsF-Q_VFRj0T4lualFKHG5oOrMd.png
502 ms
FkA2UHp5wghyBPENkt5dFcxX0AtD.png
503 ms
FpzrNbxUKvhF-RBHTZWdDTSGF_7_.png
501 ms
FmGs4YuUmRQ0lGd1tJ6zwNpnJgR-.png
509 ms
FsQuuHv6rILUeYWE-2lzQ3wC6hFQ.png
495 ms
FiGJngBlmJSv7E7o1XpIzoUztJy3.png
515 ms
FgUcTq-t4nqypL3N8CPpmAsBpTu0.png
510 ms
Fsf4JYknM8hj8YGWBaDZMixMdpbi.png
516 ms
FnK4x3X3OGcoa5OxjkZIISqHyjsa.png
518 ms
Fq7GzRMwE6LB-guA48Vp7L4FCTmK.png
517 ms
FsGBY_WEEugaV6kyQXgiQz_x5Nnl.png
522 ms
FlRrR4XGT6pCvx0K-l_azf8sRw19.png
539 ms
Fj0TrtleAmBtLzYTlp95EJmFJ6g_.png
555 ms
FpOcE4yOX4c7w2VJ0UMsJ_Q2etKV.png
559 ms
Fg7sybkOIA-6IzTf0OA0_UdgCHDP.png
552 ms
FldQfdxzZboep6R-n7ozOTfRypIU.png
546 ms
FhRQnTbcIQxHFeQG4x3hz06xKqr4.png
561 ms
Fq3a7vGlaQxH3NWyOvYFzt_BYM_S.png
567 ms
Fg1g44pxQCQH02Pge6T1wXa8aYZD.png
566 ms
Fo_nnMgYjpuQvWqd9nSKxXvUX4oR.jpg
572 ms
FspviYXRynL5xXXZmu5j0OYPLBTH.jpg
567 ms
FuUjaeBH-jmCLp6WOqzBWMWFfNmb.JPG
568 ms
Fh4liBhwlEGCL50DKernRYoHsxCL.jpg
576 ms
FjOuGXXjjPnPPHwXxADHBuNswolQ.jpg
576 ms
FvsIAwFZtcwfU_eupH4SPW8IWFm8.png
579 ms
Fusk2-7KVXzJW3SSq4T4Gqnxw8ZA.jpg
574 ms
Fow7U7zv22ZFxdySZWFyQQ-KIisR.jpg
583 ms
Fr8bLyiDNu7VKuh1W9HHb2wn-rJi.png
580 ms
Fl0sfjXmi0IrMDB3WTpzityZbswv.png
594 ms
Fvoxqp3cWxUmD00ZGnatR-pji1qn.jpg
582 ms
Fp3j9Ij9NoQ_Zc5vdbfkbyU3xNlv.jpg
589 ms
FoSnuTROpTcoS7Wt9iGB-9Qpt6jV.jpg
603 ms
paddle_prev_fff.525c063b989d5e545a0953ed272a7ba7.png
196 ms
paddle_next_fff.0e534757807692ac2e5343e66c97ab75.png
196 ms
paddle_prev_999.7298f280860519af34b943868d1bb20a.png
197 ms
paddle_next_999.2f79520c267d4d18f859e66e7bdf9e61.png
196 ms
Fs2SEWzett3WyBt2jp4UkTTYo6GV.jpg
128 ms
Fs1RqhT7-x_TFfu05XtUFAMR6Hde.png
127 ms
Fim3KmbEeKFhDTCCaXfGDGz6029i.png
113 ms
Fq2XPydHRTxi6BIqQ-H2U2Ccrai5.png
111 ms
FvzQRBqRoRQxYyGUD1OjQSFOhqCx.png
120 ms
FoU7xvYhOIr8HeCPCGX4XyfpUWKV.png
114 ms
FmgcwXt8OAZK-0dpYf1RWyswnEIU.png
111 ms
Fjvixso05Q_1hm50nGXHS3mpQESd.png
110 ms
FnjyJDouSkLydMhYaPu0mWa59pPu.png
111 ms
FsudWah1pRIHbDxzhqusAa37qaTD.png
105 ms
FokkCNjgnSH515t9Egd3F80IM0KD.png
109 ms
FjLnAQ_Q3p6HOiNC-xZQNUxSjDr5.png
116 ms
FhYZTMD0PeygmdxXNBhYpdKxn7QO.jpg
113 ms
css
223 ms
qcpt.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
qcpt.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
qcpt.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
ZH
![]()
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qcpt.org can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Qcpt.org 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.
qcpt.org
Open Graph data is detected on the main page of Qcpt. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: