Tools & Wizards About Us
epigendx.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

epigendx.com

EpigenDx | DNA Methylation and Pyrosequencing Service Laboratory

Page Load Speed

1.4 sec in total

First Response

133 ms

Resources Loaded

1.1 sec

Page Rendered

155 ms

epigendx.com screenshot

About Website

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

Provider of DNA methylation analysis services. We are experts in CpG methylation, Pyrosequencing assay design, and epigenomic applications.

Visit epigendx.com

Key Findings

We analyzed Epigendx.com page load time and found that the first response time was 133 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

epigendx.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

epigendx.com

133 ms

epigendx.com

359 ms

js

49 ms

bootstrap.min.css

63 ms

style.css

127 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 80% of them (20 requests) were addressed to the original Epigendx.com, 8% (2 requests) were made to Googletagmanager.com and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (371 ms) belongs to the original domain Epigendx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 177.5 kB (9%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Epigendx.com main page is 2.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. 40% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 15.4 kB

  • Original 19.9 kB
  • After minification 17.0 kB
  • After compression 4.5 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 2.9 kB, which is 15% 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 15.4 kB or 78% of the original size.

Image Optimization

-8%

Potential reduce by 161.1 kB

  • Original 1.9 MB
  • After minification 1.7 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. Epigen Dx images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 154 B

  • Original 82.6 kB
  • After minification 82.6 kB
  • After compression 82.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 882 B

  • Original 32.0 kB
  • After minification 32.0 kB
  • After compression 31.1 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. Epigendx.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (43%)

Requests Now

23

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epigen Dx. 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.

Network Requests Diagram

epigendx.com

epigendx.com

133 ms

epigendx.com

epigendx.com

359 ms

js

js

49 ms

bootstrap.min.css

bootstrap.min.css

63 ms

style.css

style.css

127 ms

light_style.css

light_style.css

180 ms

page-list.css

page-list.css

181 ms

font-awesome.min.css

font-awesome.min.css

182 ms

jquery.min.js

jquery.min.js

187 ms

bootstrap.min.js

bootstrap.min.js

186 ms

ga.js

ga.js

187 ms

slider.js

slider.js

232 ms

js

js

52 ms

analytics.js

analytics.js

19 ms

collect

collect

50 ms

collect

collect

72 ms

bar3.png

bar3.png

236 ms

epigendx-banner.jpg

epigendx-banner.jpg

115 ms

logo.gif

logo.gif

165 ms

pyro1.png

pyro1.png

371 ms

pgm.png

pgm.png

321 ms

array.png

array.png

320 ms

glp.jpg

glp.jpg

224 ms

clia.png

clia.png

321 ms

big_shadow.png

big_shadow.png

217 ms

Accessibility Review

epigendx.com accessibility score

93

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

epigendx.com best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

epigendx.com SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epigendx.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 Epigendx.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

epigendx.com

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