здоровое-питание.рф

Здоровое-питание.рф Test Results

Здоровое-питание.рф Mobile Performance: 46/100

Quick overview:

Opportunities

These suggestions can help your page load faster. They don't directly affect the Performance score.

Preload key requests. Potential savings of 9,600 ms

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.

Serve images in next-gen formats. Potential savings of 1,107 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Enable text compression. Potential savings of 1,003 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images. Potential savings of 771 KB

Optimized images load faster and consume less cellular data. Learn more.

Defer offscreen images. Potential savings of 623 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images. Potential savings of 464 KB

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Reduce server response times (TTFB). Root document took 1,050 ms

Time To First Byte identifies the time at which your server sends a response. Learn more.

Diagnostics

More information about the performance of your application. These numbers don't directly affect the Performance score.

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.

Serve static assets with an efficient cache policy

10 resources found

A long cache lifetime can speed up repeat visits to your page. Learn more.

Minimize main-thread work

5.8 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

Avoid enormous network payloads

Total size was 3,681 KB

Large network payloads cost users real money and are highly correlated with long load times. Learn more.

Reduce JavaScript execution time

1.8 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Avoid chaining critical requests

10 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Keep request counts low and transfer sizes small

27 requests • 3,681 KB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

User Timing marks and measures

28 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Здоровое-питание.рф Mobile SEO: 91/100

Quick overview:

Content Best Practices

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

Document does not have a meta description

Meta descriptions may be included in search results to concisely summarize page content. Learn more. Description text is empty.

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.

Tap targets are not sized appropriately

98% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Здоровое-питание.рф Mobile Best Practices: 85/100

Quick overview:

Does not use HTTPS

1 insecure request found

All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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.

Links to cross-origin destinations are unsafe

Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.

Здоровое-питание.рф Mobile Progressive Web App: 22/100

Quick overview:

PWA Optimized

Does not set a theme color for the address bar.

The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.

Is not configured for a custom splash screen

A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.

Does not provide a valid `apple-touch-icon`

For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.

Fast and reliable

Page load is not fast enough on mobile networks

Interactive at 13.2 s

A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.

`start_url` does not respond with a 200 when offline

A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.

Current page does not respond with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.

Installable

Does not use HTTPS

1 insecure request found

Web app manifest does not meet the installability requirements

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.

Does not register a service worker that controls page and `start_url`

The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.

Здоровое-питание.рф Mobile Accessibility: 80/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.

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

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

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

Similar tests

www.здоровое-питание.com
www.здоровое-питание.net
www.здоровое-питание.org
www.здоровое-питание.info
www.здоровое-питание.biz
www.здоровое-питание.us
www.здоровое-питание.mobi
www.здоровоепитание.рф
www.здоровое-питание.рф