Gen.ru Site Title

Уникальные принты и гаджеты - Интернет-магазин Gen.RU

Gen.ru Meta Description

Привет, мы — Gen.ru! У нас — команды Gen.ru — в ДНК есть особый ген. Ген свободы! Он побуждает нас не скрывать собственное мнение, делать выбор, не оглядываясь по сторонам, ломать стереотипы и шаблоны, поддерживать тех людей и те идеи, которые нам близки.

Gen.ru Test Results

Gen.ru Mobile Performance: 69/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce initial server response time
Root document took 840 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Reduce unused CSS
Potential savings of 81 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Serve images in next-gen formats
Potential savings of 2,597 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Defer offscreen images
Potential savings of 689 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused JavaScript
Potential savings of 82 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Largest Contentful Paint element
7,050 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid an excessive DOM size
2,405 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Eliminate render-blocking resources
Potential savings of 440 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 9 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Avoid enormous network payloads
Total size was 5,033 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Serve static assets with an efficient cache policy
91 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Properly size images
Potential savings of 16 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Time to Interactive
8.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
270 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Gen.ru Mobile SEO: 83/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Gen.ru Mobile Best Practices: 62/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Gen.ru Mobile Accessibility: 79/100
Quick overview:
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.
Image elements have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Similar tests
www.gen.com
www.gen.net
www.gen.org
www.gen.info
www.gen.biz
www.gen.us
www.gen.mobi
www.en.ru
www.gen.ru
www.fen.ru
www.gfen.ru
www.fgen.ru
www.ven.ru
www.gven.ru
www.vgen.ru
www.ten.ru
www.gten.ru
www.tgen.ru
www.ben.ru
www.gben.ru
www.bgen.ru
www.yen.ru
www.gyen.ru
www.ygen.ru
www.hen.ru
www.ghen.ru
www.hgen.ru
www.gn.ru
www.gwn.ru
www.gewn.ru
www.gwen.ru
www.gsn.ru
www.gesn.ru
www.gsen.ru
www.gdn.ru
www.gedn.ru
www.gden.ru
www.grn.ru
www.gern.ru
www.gren.ru
www.ge.ru
www.geb.ru
www.genb.ru
www.gebn.ru
www.geh.ru
www.genh.ru
www.gehn.ru
www.gej.ru
www.genj.ru
www.gejn.ru
www.gem.ru
www.genm.ru
www.gemn.ru
Last Tested: