Sanepid.ru Site Title

Центр гигиены и эпидемиологии в Кировской области

Sanepid.ru Meta Description

Мы оказываем услуги населению в области обеспечения санитарно-эпидемиологического благополучия населения и первичной профилактики заболеваний, занимаемся проведением аттестации рабочих мест, защитой прав потребителей

Sanepid.ru Test Results

Sanepid.ru Mobile Performance: 64/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Largest Contentful Paint element
4,230 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
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.
Avoid large layout shifts
3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Serve images in next-gen formats
Potential savings of 437 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.
Eliminate render-blocking resources
Potential savings of 1,020 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.
Reduce unused JavaScript
Potential savings of 144 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.
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Properly size images
Potential savings of 65 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 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
Efficiently encode images
Potential savings of 9 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
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
Serve static assets with an efficient cache policy
64 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Time to Interactive
4.2 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.

Sanepid.ru Mobile SEO: 92/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.

Sanepid.ru Mobile Best Practices: 66/100
Quick overview:
User Experience
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
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
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
Sanepid.ru Mobile Accessibility: 57/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.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links 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.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Similar tests
www.sanepid.com
www.sanepid.net
www.sanepid.org
www.sanepid.info
www.sanepid.biz
www.sanepid.us
www.sanepid.mobi
www.anepid.ru
www.sanepid.ru
www.wanepid.ru
www.swanepid.ru
www.wsanepid.ru
www.eanepid.ru
www.seanepid.ru
www.esanepid.ru
www.danepid.ru
www.sdanepid.ru
www.dsanepid.ru
www.zanepid.ru
www.szanepid.ru
www.zsanepid.ru
www.xanepid.ru
www.sxanepid.ru
www.xsanepid.ru
www.aanepid.ru
www.saanepid.ru
www.asanepid.ru
www.snepid.ru
www.sqnepid.ru
www.saqnepid.ru
www.sqanepid.ru
www.swnepid.ru
www.sawnepid.ru
www.ssnepid.ru
www.sasnepid.ru
www.ssanepid.ru
www.sznepid.ru
www.saznepid.ru
www.saepid.ru
www.sabepid.ru
www.sanbepid.ru
www.sabnepid.ru
www.sahepid.ru
www.sanhepid.ru
www.sahnepid.ru
www.sajepid.ru
www.sanjepid.ru
www.sajnepid.ru
www.samepid.ru
www.sanmepid.ru
www.samnepid.ru
www.sanpid.ru
www.sanwpid.ru
www.sanewpid.ru
www.sanwepid.ru
www.sanspid.ru
www.sanespid.ru
www.sansepid.ru
www.sandpid.ru
www.sanedpid.ru
www.sandepid.ru
www.sanrpid.ru
www.sanerpid.ru
www.sanrepid.ru
www.saneid.ru
www.saneoid.ru
www.sanepoid.ru
www.saneopid.ru
www.sanelid.ru
www.saneplid.ru
www.sanelpid.ru
www.sanepd.ru
www.sanepud.ru
www.sanepiud.ru
www.sanepuid.ru
www.sanepjd.ru
www.sanepijd.ru
www.sanepjid.ru
www.sanepkd.ru
www.sanepikd.ru
www.sanepkid.ru
www.sanepod.ru
www.sanepiod.ru
www.sanepi.ru
www.sanepix.ru
www.sanepidx.ru
www.sanepixd.ru
www.sanepis.ru
www.sanepids.ru
www.sanepisd.ru
www.sanepie.ru
www.sanepide.ru
www.sanepied.ru
www.sanepir.ru
www.sanepidr.ru
www.sanepird.ru
www.sanepif.ru
www.sanepidf.ru
www.sanepifd.ru
www.sanepic.ru
www.sanepidc.ru
www.sanepicd.ru
Last Tested: