Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

genopi.com

Genopi

Page Load Speed

1.7 sec in total

First Response

186 ms

Resources Loaded

1.2 sec

Page Rendered

278 ms

genopi.com screenshot

About Website

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

Web site created using create-react-app

Visit genopi.com

Key Findings

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

Performance Metrics

genopi.com performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value4.3 s

84/100

10%

Network Requests Diagram

genopi.com

186 ms

www.genopi.com

330 ms

estilos-reset.css

111 ms

estilos.css

160 ms

facebox.css

159 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 88% of them (14 requests) were addressed to the original Genopi.com, 13% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (330 ms) belongs to the original domain Genopi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 81.3 kB (23%)

Content Size

354.5 kB

After Optimization

273.2 kB

In fact, the total size of Genopi.com main page is 354.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 247.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 7.8 kB

  • Original 10.3 kB
  • After minification 8.9 kB
  • After compression 2.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 1.4 kB, which is 14% 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 7.8 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 18.1 kB

  • Original 247.6 kB
  • After minification 229.5 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. Genopi images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 45.8 kB

  • Original 84.3 kB
  • After minification 80.4 kB
  • After compression 38.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 45.8 kB or 54% of the original size.

CSS Optimization

-77%

Potential reduce by 9.5 kB

  • Original 12.3 kB
  • After minification 9.6 kB
  • After compression 2.9 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. Genopi.com needs all CSS files to be minified and compressed as it can save up to 9.5 kB or 77% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

14

After Optimization

14

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Genopi. According to our analytics all requests are already optimized.

Accessibility Review

genopi.com accessibility score

95

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.

Best Practices

genopi.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

genopi.com SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Genopi.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Genopi.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

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