8.6 sec in total
700 ms
7.3 sec
546 ms
Click here to check amazing 4 Life content. Otherwise, check out these important facts you probably never knew about 4life.cn
福莱海外购-共建健康生活
Visit 4life.cnWe analyzed 4life.cn page load time and found that the first response time was 700 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
4life.cn performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value7.8 s
3/100
25%
Value12.0 s
4/100
10%
Value1,630 ms
12/100
30%
Value0.483
17/100
15%
Value30.2 s
0/100
10%
700 ms
885 ms
1271 ms
735 ms
760 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 9% of them (8 requests) were addressed to the original 4life.cn, 37% (34 requests) were made to Img03.4life.cn and 13% (12 requests) were made to Webpage.qidian.qq.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Zgsdk.zhugeio.com.
Page size can be reduced by 523.8 kB (12%)
4.2 MB
3.7 MB
In fact, the total size of 4life.cn main page is 4.2 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. 70% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 263.2 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 263.2 kB or 94% of the original size.
Potential reduce by 41.1 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. 4 Life images are well optimized though.
Potential reduce by 179.5 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 179.5 kB or 27% of the original size.
Potential reduce by 40.0 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. 4life.cn needs all CSS files to be minified and compressed as it can save up to 40.0 kB or 19% of the original size.
Number of requests can be reduced by 46 (53%)
87
41
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 4 Life. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
4life.cn
700 ms
4life.cn
885 ms
www.4life.cn
1271 ms
lang.js
735 ms
typical.css
760 ms
moo.min.js
760 ms
ui.min.js
748 ms
zhuge_common.js
724 ms
basic.min.css
736 ms
lang.js
737 ms
shop.min.js
729 ms
widgetsproinstance-get_css-ecclub-aW5kZXguaHRtbA==.html
258 ms
bootstrap.css
732 ms
swiper.min.css
734 ms
common.css
740 ms
main.css
803 ms
jquery-1.9.1.js
861 ms
bootstrap.js
811 ms
swiper.js
879 ms
jquery.lazyload.js
811 ms
main.js
812 ms
hammer.min.js
854 ms
jquery.hammer.js
877 ms
a9f06010fa20cb6243c23a4647ee1a3a
1229 ms
545214d5fda28e8b931316d8701598ea
1247 ms
zhuge_event.js
875 ms
zhuge.min.js
1870 ms
fdcf2a0ab7.png
386 ms
e3749c7b7e.jpg
571 ms
bfc0f94de2.jpg
796 ms
4d8f729bac.jpg
244 ms
time.png
261 ms
a9afa4d9dd.jpg
582 ms
580ef492a1.jpg
682 ms
91be353c3d.jpg
757 ms
46f84a3c43.jpg
509 ms
9d3b876063.jpg
773 ms
b0dbd57857.jpg
152 ms
ticon1.png
260 ms
ticon2.png
118 ms
ticon3.png
314 ms
ticon4.png
117 ms
navbtn.png
117 ms
ticon4_new.png
117 ms
ticon3_new.png
432 ms
9be72f22f2.jpg
498 ms
bbed804903.jpg
604 ms
3c20671f56.jpg
183 ms
ficon1.png
520 ms
ficon2.png
323 ms
ficon3.png
375 ms
ficon4.png
606 ms
ficon5.png
440 ms
ficon6.png
495 ms
ficon7.png
504 ms
gan.png
559 ms
phone.png
491 ms
email.png
718 ms
610124195d.jpg
772 ms
iconfont.ttf
515 ms
pk1.js
769 ms
account.html
372 ms
i.js
9 ms
jsonp
619 ms
getGrayLevel
1031 ms
jsonp
614 ms
getGrayLevel
903 ms
trace
1801 ms
trace
1801 ms
trace
1802 ms
web.gif
1492 ms
web.gif
1489 ms
web.gif
1489 ms
web.gif
1440 ms
web.gif
1190 ms
pc.html
360 ms
index.html
1058 ms
initQidianMonitor.js
61 ms
instant.js
60 ms
qidianMonitor.umd.min.js
158 ms
feedback-1.2.27.js
84 ms
trtc_4.14.4.js
292 ms
chunk-vendors.ce592f66.css
83 ms
pc.00d1a4f9.css
86 ms
chunk-imsdk.1734d850.js
85 ms
chunk-vendors.893efb50.js
98 ms
pc.4d00104d.js
92 ms
markdown-white-loading.gif
115 ms
sendBtn.d9fa2c33.svg
26 ms
qidianMonitor.umd.min.js
26 ms
jquery-1.12.4-fixed.min.js
24 ms
statusManager.js
25 ms
icomoon.f4992c50.ttf
259 ms
4life.cn 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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
4life.cn best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
4life.cn SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 doesn't use legible font sizes
Tap targets are not sized appropriately
ZH
ZH
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 4life.cn 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 4life.cn main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
4life.cn
Open Graph description is not detected on the main page of 4 Life. 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: