Access origene.com. Home

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value16.1 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value4,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

www.origene.com

889 ms

gtm.js

84 ms

app-1620483914.css

293 ms

css2

76 ms

v_widget-2.5.css

67 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 6% of them (6 requests) were addressed to the original Origene.com, 19% (20 requests) were made to Cdn.origene.com and 13% (14 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (889 ms) belongs to the original domain Origene.com.

Content Size

3.0 MB

After Optimization

2.3 MB

In fact, the total size of Origene.com main page is 3.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 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 193.3 kB

Original 212.1 kB
After minification 105.1 kB
After compression 18.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 107.0 kB, which is 50% 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 193.3 kB or 91% of the original size.

Image Optimization

-20%

Potential reduce by 508.4 kB

Original 2.5 MB
After minification 2.0 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. Obviously, Ori Gene needs image optimization as it can save up to 508.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 9.5 kB

Original 323.6 kB
After minification 323.3 kB
After compression 314.1 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

-11%

Potential reduce by 1.8 kB

Original 16.9 kB
After minification 16.7 kB
After compression 15.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. Origene.com needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 11% of the original size.

Requests Now

After Optimization

The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ori 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 33 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

origene.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Home | OriGene

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

www.origene.com

gtm.js

app-1620483914.css

css2

v_widget-2.5.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

www.origene.com

gtm.js

app-1620483914.css

css2

v_widget-2.5.css

font-awesome-reg.css

tooltipster.css

tooltipster-theme2.css

jquery.min.js

crossword-1189438869.js

all.js

bioz-w-api-2.0.min.js

v_widget-2.5.origene.js

tooltipster.js

265016.js

jquery.rwdImageMaps.min.js

jquery.maphilight.min.js

app-2119664063.js

font-awesome-4.7.0.css

js

analytics.js

hotjar-931863.js

bat.js

insight.min.js

web-vitals.iife.js

insight_tag_errors.gif

collect

web-vitals.iife.js

US.png

DE.png

JP.png

GB.png

CN.png

IHC-validated-promotion-banner.png

Rapid-Titer-Kit.png

IHCEssentials.png

dnaPhoto.jpg

viralTools.png

antibodiesPhoto.jpg

proteinPhoto.jpg

IHCPhoto.jpg

moleculePhoto.jpg

crisprPhoto.jpg