Vk.link Site Title
Конструктор сайтов ВКонтакте: создайте сайт на основе сообщества
Vk.link Test Results
Vk.link Mobile Performance: 21/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources. Potential savings of 5,070 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Avoid multiple page redirects. Potential savings of 3,030 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Remove unused JavaScript. Potential savings of 280 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Remove unused CSS. Potential savings of 226 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Reduce initial server response time. Root document took 740 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minimize main-thread work
4.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
2.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Serve static assets with an efficient cache policy
29 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid long main-thread tasks
7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. 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
43 requests • 845 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Vk.link Mobile SEO: 100/100
Quick overview:
Vk.link Mobile Best Practices: 0/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 servedover 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.
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
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.
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more.
Browser Compatibility
Properly defines charset
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.
Vk.link Mobile Progressive Web App: 93/100
Quick overview:
Installable
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 servedover 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.
Vk.link Mobile Accessibility: 68/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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a valid value for its `[lang]` attribute.
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
`<dl>`'s do not contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Best practices
These items highlight common accessibility best practices.
`[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.
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 sites
Similar tests
www.vk.com
www.vk.net
www.vk.org
www.vk.info
www.vk.biz
www.vk.us
www.vk.mobi
www.k.link
www.vk.link
www.ck.link
www.vck.link
www.cvk.link
www.fk.link
www.vfk.link
www.fvk.link
www.gk.link
www.vgk.link
www.gvk.link
www.bk.link
www.vbk.link
www.bvk.link
www.v.link
www.vj.link
www.vkj.link
www.vjk.link
www.vi.link
www.vki.link
www.vik.link
www.vm.link
www.vkm.link
www.vmk.link
www.vl.link
www.vkl.link
www.vlk.link
www.vo.link
www.vko.link
www.vok.link
www.vk.net
www.vk.org
www.vk.info
www.vk.biz
www.vk.us
www.vk.mobi
www.k.link
www.vk.link
www.ck.link
www.vck.link
www.cvk.link
www.fk.link
www.vfk.link
www.fvk.link
www.gk.link
www.vgk.link
www.gvk.link
www.bk.link
www.vbk.link
www.bvk.link
www.v.link
www.vj.link
www.vkj.link
www.vjk.link
www.vi.link
www.vki.link
www.vik.link
www.vm.link
www.vkm.link
www.vmk.link
www.vl.link
www.vkl.link
www.vlk.link
www.vo.link
www.vko.link
www.vok.link