19.9 sec in total
651 ms
18.8 sec
465 ms
Click here to check amazing Edigene content. Otherwise, check out these important facts you probably never knew about edigene.com
EdiGene是一家生物技术公司,其使命是将前沿的基因组编辑技术转化为治疗遗传病和癌症的新疗法,并将其转化为创新的解决方案,以推进药物发现。我们利用我们的专有平台来开发针对一系列疾病的基因编辑疗法,并进行高通量的基因组筛选,以便能够在生物学环境中剖析功能性大数据。
Visit edigene.comWe analyzed Edigene.com page load time and found that the first response time was 651 ms and then it took 19.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
edigene.com performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value4.4 s
40/100
25%
Value5.2 s
60/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.2 s
99/100
10%
651 ms
908 ms
635 ms
630 ms
633 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 96% of them (50 requests) were addressed to the original Edigene.com, 4% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (15.8 sec) belongs to the original domain Edigene.com.
Page size can be reduced by 120.7 kB (10%)
1.2 MB
1.1 MB
In fact, the total size of Edigene.com main page is 1.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. 40% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 36.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. This page needs HTML code to be minified as it can gain 16.0 kB, which is 37% 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 36.8 kB or 85% of the original size.
Potential reduce by 71.9 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. Edigene images are well optimized though.
Potential reduce by 9.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.7 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. Edigene.com has all CSS files already compressed.
Number of requests can be reduced by 10 (20%)
50
40
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edigene. 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 from 5 to 1 for CSS and as a result speed up the page load time.
edigene.com
651 ms
edigene.com
908 ms
style-cn.css
635 ms
swiper.css
630 ms
jquery.fullPage.css
633 ms
style.css
843 ms
animate.min.css
638 ms
jquery.min.js
854 ms
swiper.min.js
1480 ms
jquery.fullPage.min.js
1263 ms
wow.min.js
1267 ms
lib.js
1270 ms
module.js
1473 ms
20082615205597528.png
231 ms
20082615205596491.png
628 ms
dd-bg4.jpg
631 ms
dd-logo.png
630 ms
dd-logo_b.png
637 ms
dd-so.png
638 ms
20082615205540395.png
859 ms
dd-banner1.jpg
3926 ms
dd-lx1_b.png
1262 ms
dd-lx2_b.png
1671 ms
dd-lx3_b.png
1261 ms
dd-lx4_b.png
1477 ms
dd-jt1.png
1486 ms
dd-bg5_b.png
2300 ms
dd-xt.png
2095 ms
dd-jy.png
8907 ms
dd-xd3.png
4161 ms
dd-xd.png
4778 ms
dd-xd2.png
5115 ms
dd-border.svg
2931 ms
dd-bg6.png
4385 ms
dd-light.png
4759 ms
20092513422086507.jpg
5404 ms
202212301c.jpg
5428 ms
dd-yz1.png
5800 ms
dd-yz-gs_b_l.png
5615 ms
dd-yz-gs_b_m.png
5755 ms
dd-yz-gs_b_r.png
6243 ms
dd-bg2.jpg
11767 ms
dd-bg3.jpg
9045 ms
dd-jt2.png
6383 ms
in-t1.png
13874 ms
zp5.png
15775 ms
zp6.png
10557 ms
dd-weixin.png
9532 ms
hm.js
1232 ms
wx-0606.png
9623 ms
full1.jpg
13770 ms
hm.gif
312 ms
edigene.com accessibility score
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.
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
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.
edigene.com 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
Page has valid source maps
edigene.com SEO score
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
![]()
EN
![]()
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edigene.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that Edigene.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.
edigene.com
Open Graph description is not detected on the main page of Edigene. 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: