Tools & Wizards About Us
zageno.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

zageno.com

Life Science Supplies & Lab Inventory Management - ZAGENO

Page Load Speed

474 ms in total

First Response

51 ms

Resources Loaded

373 ms

Page Rendered

50 ms

zageno.com screenshot

About Website

Click here to check amazing ZAGENO content for United States. Otherwise, check out these important facts you probably never knew about zageno.com

Improve your lab's efficiency with the life science industry's leading product marketplace and inventory management platform. See what ZAGENO can do for you.

Visit zageno.com

Key Findings

We analyzed Zageno.com page load time and found that the first response time was 51 ms and then it took 423 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

zageno.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.6 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.184

66/100

15%

TTI (Time to Interactive)

Value26.7 s

0/100

10%

Network Requests Diagram

zageno.com

51 ms

zageno.com

196 ms

gtm.js

87 ms

runtime.min.js

19 ms

importmap.json

118 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 30% of them (3 requests) were addressed to the original Zageno.com, 40% (4 requests) were made to Cdn.jsdelivr.net and 10% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (196 ms) belongs to the original domain Zageno.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 896.7 kB (54%)

Content Size

1.7 MB

After Optimization

754.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zageno.com main page is 1.7 MB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 8.5 kB

  • Original 11.9 kB
  • After minification 11.9 kB
  • After compression 3.4 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 8.5 kB or 71% of the original size.

Image Optimization

-45%

Potential reduce by 552.3 kB

  • Original 1.2 MB
  • After minification 662.6 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. Obviously, ZAGENO needs image optimization as it can save up to 552.3 kB or 45% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-44%

Potential reduce by 24.3 kB

  • Original 55.3 kB
  • After minification 55.3 kB
  • After compression 31.0 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 24.3 kB or 44% of the original size.

CSS Optimization

-85%

Potential reduce by 311.7 kB

  • Original 368.8 kB
  • After minification 368.6 kB
  • After compression 57.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. Zageno.com needs all CSS files to be minified and compressed as it can save up to 311.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (75%)

Requests Now

8

After Optimization

2

  • AJAX
  • JavaScript

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

Network Requests Diagram

zageno.com

zageno.com

51 ms

zageno.com

zageno.com

196 ms

gtm.js

gtm.js

87 ms

runtime.min.js

runtime.min.js

19 ms

importmap.json

importmap.json

118 ms

import-map-overrides.js

import-map-overrides.js

21 ms

system.min.js

system.min.js

24 ms

amd.min.js

amd.min.js

27 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

43 ms

main.js

main.js

15 ms

Accessibility Review

zageno.com accessibility score

86

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

zageno.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

zageno.com SEO score

84

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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

zageno.com

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