fc00.ru - fc00.ru

Fc00.ru Site Title

fc00.ru

Fc00.ru Test Results

Fc00.ru Mobile Performance: 62/100

Quick overview:

Diagnostics

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

Reduce JavaScript execution time

7.2 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

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

Avoid multiple page redirects

Potential savings of 600 ms

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Minimize main-thread work

9.7 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Serve images in next-gen formats

Potential savings of 11 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.

Reduce unused JavaScript

Potential savings of 1,105 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.

Reduce unused CSS

Potential savings of 50 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.

Avoid serving legacy JavaScript to modern browsers

Potential savings of 37 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

Enable text compression

Potential savings of 202 KiB

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

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.

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

Serve static assets with an efficient cache policy

34 resources found

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

Max Potential First Input Delay

1,510 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.

Time to Interactive

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

Fc00.ru Mobile SEO: 90/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 about the meta description.

Fc00.ru Mobile Best Practices: 62/100

Quick overview:

Browser Compatibility

Page lacks the HTML doctype, thus triggering quirks-mode

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document must contain a doctype

Charset declaration is missing or occurs too late in the HTML

A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

Trust and Safety

Does not use HTTPS

56 insecure requests 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.

Does not redirect HTTP traffic to HTTPS

Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.

User Experience

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`

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.

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

Missing source maps for large first-party JavaScript

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Fc00.ru Mobile Accessibility: 33/100

Quick overview:

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.

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.

`<frame>` or `<iframe>` elements do not have a title

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Similar tests

www.fc00.com
www.fc00.net
www.fc00.org
www.fc00.info
www.fc00.biz
www.fc00.us
www.fc00.mobi
www.c00.ru
www.fc00.ru
www.cc00.ru
www.fcc00.ru
www.cfc00.ru
www.dc00.ru
www.fdc00.ru
www.dfc00.ru
www.rc00.ru
www.frc00.ru
www.rfc00.ru
www.tc00.ru
www.ftc00.ru
www.tfc00.ru
www.gc00.ru
www.fgc00.ru
www.gfc00.ru
www.vc00.ru
www.fvc00.ru
www.vfc00.ru
www.f00.ru
www.fx00.ru
www.fcx00.ru
www.fxc00.ru
www.fd00.ru
www.fcd00.ru
www.ff00.ru
www.fcf00.ru
www.ffc00.ru
www.fv00.ru
www.fcv00.ru
www.fc0.ru