Tools & Wizards About Us
excellgene.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

excellgene.com

Home - ExcellGene SA

Page Load Speed

4.6 sec in total

First Response

890 ms

Resources Loaded

3.2 sec

Page Rendered

528 ms

excellgene.com screenshot

About Website

Welcome to excellgene.com homepage info - get ready to check Excell Gene best content right away, or after learning these important things about excellgene.com

Cutting-edge CHO and HEK Cell Lines & Production Processes. High Yielding, Fast, Scalable, Guaranteed.

Visit excellgene.com

Key Findings

We analyzed Excellgene.com page load time and found that the first response time was 890 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

excellgene.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.866

4/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

excellgene.com

890 ms

wpa.css

190 ms

choices.min.css

288 ms

intl-tel-input.min.css

431 ms

richtext.min.css

330 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 43% of them (35 requests) were addressed to the original Excellgene.com, 39% (32 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Client.crisp.chat. The less responsive or slowest element that took the longest time to load (890 ms) belongs to the original domain Excellgene.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 378.9 kB (22%)

Content Size

1.7 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Excellgene.com main page is 1.7 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 781.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 259.9 kB

  • Original 332.2 kB
  • After minification 327.3 kB
  • After compression 72.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 259.9 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 46.2 kB

  • Original 781.2 kB
  • After minification 735.0 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. Excell Gene images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 54.2 kB

  • Original 481.6 kB
  • After minification 481.6 kB
  • After compression 427.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 54.2 kB or 11% of the original size.

CSS Optimization

-15%

Potential reduce by 18.6 kB

  • Original 121.1 kB
  • After minification 120.8 kB
  • After compression 102.5 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. Excellgene.com needs all CSS files to be minified and compressed as it can save up to 18.6 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (79%)

Requests Now

48

After Optimization

10

  • Images
  • JavaScript
  • CSS

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Excell Gene. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

excellgene.com

excellgene.com

890 ms

wpa.css

wpa.css

190 ms

choices.min.css

choices.min.css

288 ms

intl-tel-input.min.css

intl-tel-input.min.css

431 ms

richtext.min.css

richtext.min.css

330 ms

content.min.css

content.min.css

331 ms

wpforms-modern-full.min.css

wpforms-modern-full.min.css

333 ms

style.css

style.css

293 ms

script.min.js

script.min.js

384 ms

jquery.min.js

jquery.min.js

496 ms

jquery-migrate.min.js

jquery-migrate.min.js

427 ms

js

js

65 ms

et-divi-customizer-global.min.css

et-divi-customizer-global.min.css

345 ms

39625141.js

39625141.js

89 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

355 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

397 ms

wpa.js

wpa.js

441 ms

l.js

l.js

26 ms

scripts.min.js

scripts.min.js

725 ms

smoothscroll.js

smoothscroll.js

442 ms

jquery.fitvids.js

jquery.fitvids.js

444 ms

easypiechart.js

easypiechart.js

494 ms

salvattore.js

salvattore.js

508 ms

common.js

common.js

542 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

722 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

541 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

591 ms

style.css

style.css

398 ms

gtm.js

gtm.js

100 ms

layouthorizontal-bgon-light-slogantrue-orangetrue@4x.png

layouthorizontal-bgon-light-slogantrue-orangetrue@4x.png

167 ms

preloader.gif

preloader.gif

167 ms

Depositphotos_210257742_XL-scaled.jpg

Depositphotos_210257742_XL-scaled.jpg

391 ms

Biomanufacturing_BG_1200x628px.jpg

Biomanufacturing_BG_1200x628px.jpg

435 ms

BPIWest_BG_Post_1200x628px.jpg

BPIWest_BG_Post_1200x628px.jpg

291 ms

BioEuropeSpring_BG_Post_1200x628px.jpg

BioEuropeSpring_BG_Post_1200x628px.jpg

299 ms

layouthorizontal-bgon-dark-sloganfalse-orangefalse@4x.png

layouthorizontal-bgon-dark-sloganfalse-orangefalse@4x.png

209 ms

iso9001.png

iso9001.png

209 ms

loader_22.js

loader_22.js

104 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZs.woff

61 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZg.ttf

61 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZs.woff

66 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf

65 ms

font

font

65 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf

64 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZs.woff

71 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZg.ttf

72 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeMZs.woff

77 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeMZg.ttf

72 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZs.woff

71 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

75 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZs.woff

80 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf

88 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZs.woff

87 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZg.ttf

86 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZs.woff

85 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZg.ttf

87 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE-_G.woff

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE-_G.woff

91 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE-_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE-_F.ttf

92 ms

font

font

121 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E-_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E-_F.ttf

92 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE-_G.woff

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE-_G.woff

93 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE-_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE-_F.ttf

93 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFO_G.woff

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFO_G.woff

94 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFO_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFO_F.ttf

100 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FO_G.woff

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FO_G.woff

100 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FO_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FO_F.ttf

101 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_G.woff

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_G.woff

101 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_F.ttf

101 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FO_G.woff

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FO_G.woff

103 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FO_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FO_F.ttf

102 ms

modules.woff

modules.woff

262 ms

et-divi-dynamic-tb-31294-32162-late.css

et-divi-dynamic-tb-31294-32162-late.css

123 ms

polyfill.js

polyfill.js

65 ms

app.js

app.js

103 ms

l.js

l.js

19 ms

app.bundle.min.css

app.bundle.min.css

39 ms

app.bundle.min.js

app.bundle.min.js

42 ms

collectedforms.js

collectedforms.js

100 ms

banner.js

banner.js

195 ms

39625141.js

39625141.js

144 ms

client.js

client.js

30 ms

client_legacy.css

client_legacy.css

49 ms

Accessibility Review

excellgene.com accessibility score

83

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

excellgene.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

excellgene.com SEO score

93

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

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

High

Document uses legible font sizes

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 Excellgene.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 Excellgene.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

excellgene.com

Open Graph data is detected on the main page of Excell Gene. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: