3 sec in total
77 ms
1.8 sec
1.1 sec
Welcome to communitytest.prenetics.com homepage info - get ready to check Communitytest Prenetics best content for China right away, or after learning these important things about communitytest.prenetics.com
Visit communitytest.prenetics.comWe analyzed Communitytest.prenetics.com page load time and found that the first response time was 77 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
communitytest.prenetics.com performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value10.5 s
0/100
25%
Value5.5 s
55/100
10%
Value180 ms
92/100
30%
Value0
100/100
15%
Value6.9 s
54/100
10%
77 ms
952 ms
54 ms
51 ms
103 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Communitytest.prenetics.com, 15% (11 requests) were made to Fonts.gstatic.com and 11% (8 requests) were made to Uploads-ssl.webflow.com. The less responsive or slowest element that took the longest time to load (952 ms) relates to the external source Prenetics.com.
Page size can be reduced by 319.3 kB (3%)
10.0 MB
9.7 MB
In fact, the total size of Communitytest.prenetics.com main page is 10.0 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. 75% 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 9.8 MB which makes up the majority of the site volume.
Potential reduce by 26.8 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 26.8 kB or 79% of the original size.
Potential reduce by 289.5 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. Communitytest Prenetics images are well optimized though.
Potential reduce by 503 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.
Potential reduce by 2.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. Communitytest.prenetics.com has all CSS files already compressed.
Number of requests can be reduced by 13 (25%)
51
38
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Communitytest Prenetics. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
communitytest
77 ms
www.prenetics.com
952 ms
prenetics-dot-com.webflow.634128f39.css
54 ms
webfont.js
51 ms
js
103 ms
optimize.js
99 ms
jquery-3.5.1.min.dc5e7f18c8.js
50 ms
webflow.b801acfed.js
67 ms
css
49 ms
gr
182 ms
641ddf820ddd598075f1c5f9_prenetics-Logo.svg
117 ms
64930240443cac308f69a0cb_pre_atf_bg%201.jpg
310 ms
6493024061b26974232346f5_pre_atf_family%201.png
307 ms
6497a55655bba6c4117598d0_MOBILE_KV.jpg
246 ms
648d7c2ff915136724ef30f7_Frame%20237755.jpg
116 ms
648d7c2fbdcb44458770c4df_Frame%20237754.jpg
117 ms
648d7c2ff1237afd40bbcf33_Frame%20237753.jpg
222 ms
649d44bf393b845daa2c78b8_Danny%20Insighta%20Presentation%20PC_dy%201.jpg
245 ms
649d455158749e3e30a1a7e9_Vector-00.svg
179 ms
649d44bf393b845daa2c78bc_Danny%20Insighta%20Presentation%20PC_dy%202.jpg
274 ms
649d48348b2660e3b58a7551_Vector-000.svg
230 ms
649d490aba75cbd9272cb408_Rectangle%2022758.svg
348 ms
649d4b206feeb793c9c53ad9_Group%20237774.svg
260 ms
649d490a041e855ca81a3b5f_Rectangle%2022760.svg
274 ms
649d4b20f8d3068ddb97f137_Group%20237634.svg
278 ms
65c45cf425cb62f5bab4e16f_logo_actg.svg
292 ms
648d7d4bf1237afd40bcbc2c_Vector.svg
339 ms
648d7dfcbe01f6d67de7a6a5_Group%20237634.png
342 ms
641ec1047e17a62bffea420f_arrow-white.svg
343 ms
648d7edcc0fd1cc0a5e17a73_Frame%20237713.png
388 ms
648d7dfcf1237afd40bd5d46_Group%20237649.png
381 ms
64981502a3892af8b2269ea7_desktop_early-detection-img.png
416 ms
65e582e11e32529c0764899b_logo_actg_blue.png
380 ms
648ea6bc32f94fd8cc484d14_Frame%20237712.png
462 ms
641e987ec109c41e8a11f6ef_arrow-green.svg
347 ms
65cc67b54a43de1ff7d4a2da_Frame%20237787.jpg
411 ms
65cc66aa61b0a38a3131634e_Frame%2047915.jpg
418 ms
6498e0d5f8c93e23802bd4af_insighta.jpg
410 ms
64267bc45a034a8d358f2d46_CNBC.svg
446 ms
648ea03d5ddfea7c1b2eb9a7_Group%20237714.svg
455 ms
64267bc4b8b80c728d3d75b7_SCMP.svg
498 ms
64267bc4f501d056be022c19_Guardian.svg
482 ms
64267bc471eb3db5c53ee56b_Telegraph.svg
451 ms
64267bc4a75f4e159a520187_Sky.svg
492 ms
64968d962ccff33608460b45_Group%2020.svg
500 ms
648ea38631dfd0f345a4a5b6_insta.svg
505 ms
js
99 ms
analytics.js
158 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE9_C-bw.ttf
141 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE9_C-bw.ttf
174 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E9_C-bw.ttf
204 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFN_C-bw.ttf
193 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FN_C-bw.ttf
209 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFN_C-bw.ttf
208 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FN_C-bw.ttf
207 ms
635b8130899208dcb0756b0c_Gilroy-SemiBold.ttf
255 ms
635b8130899208d4e0756b02_Gilroy-ExtraBold.ttf
279 ms
635b81308992086caa756aff_Gilroy-Black.ttf
258 ms
635b81308992087f69756b00_Gilroy-Medium.ttf
277 ms
635b81308992080594756b08_Gilroy-Regular.ttf
277 ms
635b813089920820a6756afd_Gilroy-Light.ttf
275 ms
635b8130899208d55e756b0a_Gilroy-UltraLight.ttf
339 ms
635b81308992083f0f756b06_Gilroy-Thin.ttf
389 ms
jizaRExUiTo99u79D0KEwA.ttf
209 ms
jizfRExUiTo99u79B_mh0O6tKA.ttf
210 ms
jizYRExUiTo99u79D0e0x8mN.ttf
209 ms
jizdRExUiTo99u79D0e8fOydLxUY.ttf
212 ms
648ea38634f6ea7a02b2f509_fb.svg
368 ms
648ea3865ddfea7c1b3088a4_tw.svg
424 ms
648ea386dfc7f86e442c397f_lin.svg
439 ms
js
43 ms
collect
30 ms
collect
33 ms
ga-audiences
38 ms
communitytest.prenetics.com 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.
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
Links do not have a discernible name
communitytest.prenetics.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
communitytest.prenetics.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Communitytest.prenetics.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 Communitytest.prenetics.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.
communitytest.prenetics.com
Open Graph description is not detected on the main page of Communitytest Prenetics. 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: