Brazil · Sao Paulo Completed: Apr 16, 2026 18:21 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 69 / 100
Based on 6 categories, 0 sections
Room to improve — your 13.6s load time is above Google's 2.5s 'Good' threshold.
Good foundation, but a few gaps could be exploited.
Several issues make your site difficult for assistive technology users.
Good server performance with room for optimization.
Mostly compliant — a few items need attention.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
199 third-party resources (100% of weight)
Performance issues directly impact user engagement and conversion rates.
200 HTTP requests — consider bundling or reducing
Performance issues directly impact user engagement and conversion rates.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/cbac2d33-c7c3-45e8-9e8d-7804dbd2ac96)<a href="https://beavercheck.com/results/cbac2d33-c7c3-45e8-9e8d-7804dbd2ac96"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Flivejournal.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Flivejournal.comThis badge auto-updates with your latest scan result.
Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 13.6s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your user trust.
6 barrier(s) likely increasing bounce by ~37%.
Page takes 13.6s to load
+12% bounceUsers abandon at ~3s — you're 11.1s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 2.2s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Severe layout shift during page load
+6% bounceUsers mis-click when content jumps — converting intent into frustration
Fix: Reserve space for images, ads, and embeds with explicit width/height
No viewport meta tag
+15% bounceMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
₽19,250 investment → ₽20,004/month returns
₽19,250
6h · 5 findings
₽20,004 /mo
~₽240,051 / year
No applicable regulations in this jurisdiction
₽5,250 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
5.5 developer hours at ₽3500/hr
Based on Russia rates (₽3500/hr)
Start here for the best return on investment
₽62 / month at risk
~₽741 / year if left unfixed
₽62 /mo
8491.0 MB/mo × 7.273 RUB/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 3 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
8.63 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
13.64 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.16 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.500
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
16.54 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
28.09 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| l-stat.livejournal.net/??proximanova-opentype.css?v=1776255133 | 337.1 KiB | 2.1 s |
| /??widgets/likes.css,main_v3.css,promo_wrappers.css,entry... | 27.1 KiB | 257 ms |
| /??schemius_v4/header_v5.css,schemius_v4/menu-aside.css,s... | 71.2 KiB | 1.8 s |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
LiveJournal is a unique place where people share their life stories, give advic… div.l-flatslide-body > div.l-flatslide-wrapper > div.l-flatslide-content > div.getstartedwithlj | l-stat.livejournal.net/img/widget/getstartedwithlj/bg.jpg?v=70219 | 215.6 KiB | 11.7 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
Performance issues directly impact user engagement and conversion rates.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| livejournal.com/ | 1.5 s |
| www.livejournal.com/ | 0.0 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| www.livejournal.com/ | 1.1 s |
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
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
body.s-schemius > div.s-layout > ::after body.s-schemius > div.s-layout > ::after | 0.359 |
APPLICATIONS
Download
Huawei
RuStore
FOLLOW US:
LiveJournal
COMPANY
About
Ne… body.s-schemius > footer.main-footer | 0.141 |
LOG IN div.s-layout > header.s-header > div.s-header-in > nav.s-nav | 0.001 |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| l-stat.livejournal.net/??proximanova-opentype.css?v=1776255133 | 337.0 KiB | 337.0 KiB |
| /??schemius_v4/header_v5.css,schemius_v4/menu-aside.css,s... | 71.0 KiB | 66.9 KiB |
| /??widgets/likes.css,main_v3.css,promo_wrappers.css,entry... | 27.0 KiB | 24.2 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| l-stat.livejournal.net/js/??.ljlib.js?v=1776255133 | 379.8 KiB | 187.7 KiB |
| yastatic.net/partner-code-bundles/1304600/24ec1381af6bc52b.js | 129.5 KiB | 103.0 KiB |
| /js/??old/backboneMainpage/ljtoday.js,old/backboneMainpag... | 179.9 KiB | 71.8 KiB |
| yandex.ru/ads/system/context.js | 103.4 KiB | 51.3 KiB |
| mc.webvisor.org/metrika/tag_ww.js | 84.8 KiB | 48.3 KiB |
| id.sber.ru/sdk/web/sberid-sdk.production.js | 82.6 KiB | 43.4 KiB |
| ssp.rambler.ru/capirs_async.js | 88.3 KiB | 37.0 KiB |
| /f/AGSKWxW4FWZuUtdQFTVPtyUM4nsYfj3wG8QdpDhzmDLVqXGEglR_b9... | 68.5 KiB | 36.1 KiB |
| st.top100.ru/top100/top100.js | 36.6 KiB | 27.1 KiB |
| yastatic.net/partner-code-bundles/1304600/e32796170bd90254.js | 31.8 KiB | 25.1 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| l-stat.livejournal.net/js/??.ljlib.js?v=1776255133 | 2.9 s | 2.3 s | 189 ms |
| www.livejournal.com/ | 1.2 s | 74 ms | 52 ms |
| Unattributable | 1.2 s | 48 ms | 0.0 ms |
| st.top100.ru/top100/top100.js | 581 ms | 456 ms | 52 ms |
| ssp.rambler.ru/capirs_async.js | 538 ms | 413 ms | 52 ms |
| yandex.ru/ads/system/context.js | 505 ms | 424 ms | 50 ms |
| /js/??old/backboneMainpage/ljtoday.js,old/backboneMainpag... | 405 ms | 299 ms | 95 ms |
| privacy-cs.mail.ru/static/sync-loader.js | 378 ms | 330 ms | 11 ms |
| mc.webvisor.org/metrika/tag_ww.js | 325 ms | 245 ms | 35 ms |
| yastatic.net/partner-code-bundles/1304600/24ec1381af6bc52b.js | 256 ms | 155 ms | 94 ms |
| /f/AGSKWxW4FWZuUtdQFTVPtyUM4nsYfj3wG8QdpDhzmDLVqXGEglR_b9... | 242 ms | 190 ms | 28 ms |
| top-fwz1.mail.ru/js/code.js | 105 ms | 88 ms | 6.9 ms |
| vp.rambler.ru/player/sdk.js | 101 ms | 92 ms | 7.3 ms |
| yastatic.net/partner-code-bundles/1304600/e32796170bd90254.js | 60 ms | 37 ms | 22 ms |
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 5.4 s |
| Other | 1.8 s |
| Script Parsing & Compilation | 763 ms |
| Style & Layout | 717 ms |
| Parse HTML & CSS | 304 ms |
| Garbage Collection | 162 ms |
| Rendering | 141 ms |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
body.s-schemius > div#hello-world > img body.s-schemius > div#hello-world > img | /ljcounter/?d=srv:3dt-ws05,r:0,j:0,uri:%22%2F%22,vig:0,m:... |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.s-layout > header.s-header > div.s-header-in > button.s-nav-control div.s-layout > header.s-header > div.s-header-in > button.s-nav-control |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
span.entryunit__author > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead span.entryunit__author > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
English
Deutsch
Dansk
español
Français
Italiano
Русский
Українська
Беларуская
日… div.main-footer__middle > div.main-footer__lang > div.main-footer__lang-select > select#footer_lang_list |
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body.s-schemius > iframe body.s-schemius > iframe |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
li.meta-entryunit__item > span.entryunit__author > span.ljuser > a.i-ljuser-profile li.meta-entryunit__item > span.entryunit__author > span.ljuser > a.i-ljuser-profile |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
1. ul.meta-entryunit__items > li.meta-entryunit__item > span.entryunit__position > span.position-entryunit__number |
NEWS span.entryunit__author > span.ljuser > a.i-ljuser-username > b |
december 17, 16:01 div.entryunit__meta > ul.meta-entryunit__items > li.meta-entryunit__item > time.entryunit__date |
109 div.entryunit__toolbar > div.entryunit-toolbar__item > a.ljlikus--like > span.ljlikus-counter |
SHOW MORE ENTRIES div.l-flatslide-content > div.b-entryunits-more > a.b-entryunits-more-button > span.b-entryunits-more-button-inner |
COMPANY div.main-footer__middle > div.main-footer__nav > div.main-footer__nav-group > h3.main-footer__nav-title |
PRODUCTS div.main-footer__middle > div.main-footer__nav > div.main-footer__nav-group > h3.main-footer__nav-title |
COMMUNITY div.main-footer__middle > div.main-footer__nav > div.main-footer__nav-group > h3.main-footer__nav-title |
CHOOSE LANGUAGE div.main-footer__container > div.main-footer__middle > div.main-footer__lang > h3.main-footer__lang-title |
v.916.1 div.main-footer__container > div.main-footer__bottom > p.main-footer__copyright > a |
These are opportunities to improve the legibility of your content.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Join in and create your own personal calendar for 2026! div.b-entryunits > article.entryunit > header.entryunit__head > h3.entryunit__title |
These are opportunities to improve keyboard navigation in your application.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
mc.webvisor.org/metrika/tag_ww.js line 461, col 10 | Connecting to 'wss://mc.yandex.com/solid.ws' violates the following Content Security Policy directive: "connect-src 'self' *.livejournal.com *.livejournal.net ad.adriver.ru ad.mail.ru *.ad-tech.ru api.giphy.com bs.serving-sys.ru cdn.ampproject.org *.criteo.com csi.gstatic.com data00.adlooxtracking.com dsp-rambler.ru *.dsp-rambler.ru *.eaglecdn.com event.top100.su export-download.canva.com ext.clickstream.sberbank.ru sdk.canva.com *.g.doubleclick.net googleads.g.doubleclick.net *.google-analytics.com *.googleapis.com *.google.com google.com *.googletagmanager.com googletagmanager.com graph.facebook.com gstatic.com id.sber.ru *.lj.ru lj.stat.eagleplatform.com mc.yandex.by mc.yandex.com mc.yandex.md mc.yandex.ru pingback.giphy.com *.pingdom.net privacy-cs.mail.ru *.rambler-co.ru rambler-co.ru *.rambler.ru rambler.ru rb.infox.sg *.rnet.plus *.services.livejournal.com *.ssp.rambler.ru ssp.rambler.ru static-mon.yandex.net static.xx.fbcdn.net stat.media stats.g.doubleclick.net smi2.net smi2.ru sve.online.sberbank.ru *.tiktok.com tiktok.com top-fwz1.mail.ru *.twitter.com *.webturn.ru *.webvisor.org wss://mc.yandex.ru wss://www.livejournal.com yandexmetrica.com yandexmetrica.com:29010 yandexmetrica.com:30103 *.yandex.net *.yandex.ru yandex.ru yastatic.net ymetrica1.com ymetrica.com *.youtube.com youtube.com". The action has been blocked. |
Failed to load resource: the server responded with a status of 555 () | |
Failed to load resource: the server responded with a status of 555 () |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Content security policy |
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.
Performance issues directly impact user engagement and conversion rates.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| www.livejournal.com/support/faq/350.html | here |
| www.livejournal.com/shop/commpromo.bml | here |
| www.livejournal.com/support/faq/373.html | here |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
span.entryunit__author > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead span.entryunit__author > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
Format your HTML in a way that enables crawlers to better understand your app’s content.
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
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
Mark entry as readMark entry as unr… div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link |
Hide authorBring author back div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link |
div.ng-isolate-scope > div.b-ljpromo > div.b-ljpromo-container > a.b-ljpromo-nav |
div.ng-isolate-scope > div.b-ljpromo > div.b-ljpromo-container > a.b-ljpromo-nav |
Mark entry as readMark entry as unr… div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link |
Hide authorBring author back div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link |
div.ng-isolate-scope > div.b-ljpromo > div.b-ljpromo-container > a.b-ljpromo-nav |
div.ng-isolate-scope > div.b-ljpromo > div.b-ljpromo-container > a.b-ljpromo-nav |
Show New Entries div.l-flatslide-wrapper > div.l-flatslide-content > p.b-mainpage-uprating > a.b-mainpage-uprating-inner |
Mark entry as readMark entry as unr… div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link |
Hide authorBring author back div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link |
Today header.b-topten-head > ul.b-topten-switcher > li.b-topten-switcher-item > a.b-pseudo |
All Time header.b-topten-head > ul.b-topten-switcher > li.b-topten-switcher-item > a.b-pseudo |
Today header.b-topten-head > ul.b-topten-switcher > li.b-topten-switcher-item > a.b-pseudo |
All Time header.b-topten-head > ul.b-topten-switcher > li.b-topten-switcher-item > a.b-pseudo |
Skip footer.b-helptour-footer > ul.b-helptour-controls > li.b-helptour-control > a.b-helptour-skip-link |
Prev footer.b-helptour-footer > ul.b-helptour-controls > li.b-helptour-control > a.b-helptour-prev-link |
Next footer.b-helptour-footer > ul.b-helptour-controls > li.b-helptour-control > a.b-helptour-next-link |
Done footer.b-helptour-footer > ul.b-helptour-controls > li.b-helptour-control > a.b-helptour-done-link |
Hide multiple posts from the same account ul.b-mainpage-settings > li.b-mainpage-settings-item > span.b-mainpage-settings-different > a.b-pseudo |
Show multiple posts from the same account ul.b-mainpage-settings > li.b-mainpage-settings-item > span.b-mainpage-settings-different > a.b-pseudo |
Hide posts from friends ul.b-mainpage-settings > li.b-mainpage-settings-item > span.b-mainpage-settings-friends > a.b-pseudo |
Show posts from friends ul.b-mainpage-settings > li.b-mainpage-settings-item > span.b-mainpage-settings-friends > a.b-pseudo |
Hide read posts & blocked usersHide back hidden posts from rating ul.b-mainpage-settings > li.b-mainpage-settings-item > span.b-mainpage-settings-hidden > a.b-pseudo |
Show hidden postsShow hidden posts in rating ul.b-mainpage-settings > li.b-mainpage-settings-item > span.b-mainpage-settings-hidden > a.b-pseudo |
To appear in search results, crawlers need access to your app.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
3.91 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.94 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
120 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.157
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
4.90 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
6.05 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| l-stat.livejournal.net/??proximanova-opentype.css?v=1776255133 | 337.1 KiB | 437 ms |
| /??schemius_v4/header_v5.css,schemius_v4/menu-aside.css,s... | 71.2 KiB | 819 ms |
| /??widgets/likes.css,main_v3.css,promo_wrappers.css,entry... | 27.4 KiB |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| mc.webvisor.org/metrika/tag_ww.js | 3600.0 s | 85.5 KiB |
| st.top100.ru/top100/top100.js | 0.0 ms | 36.9 KiB |
| id.sber.ru/sdk/web/sberid-sdk.production.js | 86400.0 s | 86.5 KiB |
| privacy-cs.mail.ru/static/sync-loader.js | 600.0 s | 21.9 KiB |
| vp.rambler.ru/player/sdk.js | 300.0 s | 18.4 KiB |
| st.top100.ru/top100/3.18.16/usability.js | 0.0 ms | 3.8 KiB |
| vk.ru/dist/public/api/openapi.6ed04a4cc80655f4384429e1d969f6ff.js?168 | 345600.0 s | 17.5 KiB |
| sb.scorecardresearch.com/beacon.js | 86400.0 s | 6.8 KiB |
| st.top100.ru/top100/3.18.16/mgc.js | 0.0 ms | 1.5 KiB |
| /ljcounter/?d=srv:kr-ws13,r:0,j:0,uri:%22%2F%22,vig:0,m:0... | 0.0 ms | 704 B |
| mc.yandex.com/metrika/advert.gif?t=gdpr(14)ti(4) | 3600.0 s | 614 B |
| /sync_cookie_image_decide?cid=27737346&scid=3d454ef9-4054... | 0.0 ms | 257 B |
| /sync_cookie_image_decide_secondary?cid=27737346&scid=24e... | 0.0 ms | 256 B |
| /sync_cookie_image_decide_secondary?cid=27737346&scid=24e... | 0.0 ms | 245 B |
| /sync_cookie_image_decide?cid=27737346&scid=3d454ef9-4054... | 0.0 ms | 67 B |
| pagead2.googlesyndication.com/pagead/osd.js?fcd=true | 3600.0 s | 76 B |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
LiveJournal is a unique place where people share their life stories, give advic… div.l-flatslide-body > div.l-flatslide-wrapper > div.l-flatslide-content > div.getstartedwithlj | l-stat.livejournal.net/img/widget/getstartedwithlj/bg.jpg?v=70219 | 215.6 KiB | 11.7 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| livejournal.com/ | 905 ms |
| www.livejournal.com/ | 0.0 ms |
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
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
body.s-schemius > div.s-layout > ::after body.s-schemius > div.s-layout > ::after | 0.156 |
TOP COMMUNITIES
TODAYALL TIME
1
OHNOTHEYDIDNT
2
THEQUESTIONCLUB
3
OMONATHEYDIDN… div.l-flatslide-body > div.l-flatslide-aside > div.l-flatslide-aside-content > div.page-sidebar-item | 0.001 |
1.
NEWSdecember 17, 16:01
Join in and create your own personal calendar for 20… div.l-flatslide-body > div.l-flatslide-wrapper > div.l-flatslide-content > div.b-entryunits | 0.000 |
LOG IN
JOIN FREE
ENGLISH (EN) div.s-layout > header.s-header > div.s-header-in > nav.s-nav-actions | 0.000 |
LOG IN
JOIN FREE
ENGLISH (EN) div.s-layout > header.s-header > div.s-header-in > nav.s-nav-actions | 0.000 |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| l-stat.livejournal.net/??proximanova-opentype.css?v=1776255133 | 336.9 KiB | 336.9 KiB |
| /??schemius_v4/header_v5.css,schemius_v4/menu-aside.css,s... | 71.0 KiB | 66.3 KiB |
| /??widgets/likes.css,main_v3.css,promo_wrappers.css,entry... | 27.0 KiB | 24.0 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| l-stat.livejournal.net/js/??.ljlib.js?v=1776255133 | 379.8 KiB | 192.1 KiB |
| /js/??old/backboneMainpage/ljtoday.js,old/backboneMainpag... | 179.9 KiB | 71.5 KiB |
| mc.webvisor.org/metrika/tag_ww.js | 84.8 KiB | 48.4 KiB |
| id.sber.ru/sdk/web/sberid-sdk.production.js | 82.6 KiB | 43.4 KiB |
| /f/AGSKWxW4FWZuUtdQFTVPtyUM4nsYfj3wG8QdpDhzmDLVqXGEglR_b9... | 68.5 KiB | 36.1 KiB |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
body.s-schemius > div#hello-world > img body.s-schemius > div#hello-world > img | /ljcounter/?d=srv:kr-ws13,r:0,j:0,uri:%22%2F%22,vig:0,m:0... |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
li.s-header-item > div.s-header-search > form.s-header-search__form > button.s-header-search__btn li.s-header-item > div.s-header-search > form.s-header-search__form > button.s-header-search__btn |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
span.entryunit__author > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead span.entryunit__author > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.b-mainpage-intro-content > div.b-mainpage-region > div.b-selectus-wrapper > input.b-selectus-input div.b-mainpage-intro-content > div.b-mainpage-region > div.b-selectus-wrapper > input.b-selectus-input |
div.main-footer__lang > div.main-footer__lang-select > div.b-selectus-wrapper > input.b-selectus-input div.main-footer__lang > div.main-footer__lang-select > div.b-selectus-wrapper > input.b-selectus-input |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
li.meta-entryunit__item > span.entryunit__author > span.ljuser > a.i-ljuser-profile li.meta-entryunit__item > span.entryunit__author > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile ul.b-topten-items > li.b-topten-item > span.ljuser > a.i-ljuser-profile |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
JOIN FREE ul.s-do > li.s-nav-item > a.s-header-button-blue > span.s-header-button-blue__long |
NON-CYRILLIC div.b-mainpage-region > div.b-selectus-wrapper > div.b-selectus > p.label |
1. ul.meta-entryunit__items > li.meta-entryunit__item > span.entryunit__position > span.position-entryunit__number |
NEWS span.entryunit__author > span.ljuser > a.i-ljuser-username > b |
december 17, 16:01 div.entryunit__meta > ul.meta-entryunit__items > li.meta-entryunit__item > time.entryunit__date |
109 div.entryunit__toolbar > div.entryunit-toolbar__item > a.ljlikus--like > span.ljlikus-counter |
TOP JOURNALS div.page-sidebar-item > div.b-topten > header.b-topten-head > h3.b-topten-title |
ALL TIME header.b-topten-head > ul.b-topten-switcher > li.b-topten-switcher-item > a.b-pseudo |
STEWIE_E li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
QUEENURSULA li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
LOYAL_FR li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
SESTRA_MILO li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
TRIM_C li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
MASTIPHAL25 li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
A_FILES06 li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
SPIKESGIRL58 li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
MAMAYANKA li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
NWHYTE li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
TOP COMMUNITIES div.page-sidebar-item > div.b-topten > header.b-topten-head > h3.b-topten-title |
ALL TIME header.b-topten-head > ul.b-topten-switcher > li.b-topten-switcher-item > a.b-pseudo |
OHNOTHEYDIDNT li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
THEQUESTIONCLUB li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
OMONATHEYDIDNT li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
EGL_COMM_SALES li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
EGL li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
ONTD_POLITICAL li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
PKMNCOLLECTORS li.b-topten-item > span.ljuser > a.i-ljuser-username > b.ng-binding |
COMPANY div.main-footer__middle > div.main-footer__nav > div.main-footer__nav-group > h3.main-footer__nav-title |
PRODUCTS div.main-footer__middle > div.main-footer__nav > div.main-footer__nav-group > h3.main-footer__nav-title |
COMMUNITY div.main-footer__middle > div.main-footer__nav > div.main-footer__nav-group > h3.main-footer__nav-title |
CHOOSE LANGUAGE div.main-footer__container > div.main-footer__middle > div.main-footer__lang > h3.main-footer__lang-title |
ENGLISH div.main-footer__lang-select > div.b-selectus-wrapper > div.b-selectus > p.label |
v.916.1 div.main-footer__container > div.main-footer__bottom > p.main-footer__copyright > a |
These are opportunities to improve the legibility of your content.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Join in and create your own personal calendar for 2026! div.b-entryunits > article.entryunit > header.entryunit__head > h3.entryunit__title |
These are opportunities to improve keyboard navigation in your application.
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
mc.webvisor.org/metrika/tag_ww.js line 461, col 10 | Connecting to 'wss://mc.yandex.com/solid.ws' violates the following Content Security Policy directive: "connect-src 'self' *.livejournal.com *.livejournal.net ad.adriver.ru ad.mail.ru *.ad-tech.ru api.giphy.com bs.serving-sys.ru cdn.ampproject.org *.criteo.com csi.gstatic.com data00.adlooxtracking.com dsp-rambler.ru *.dsp-rambler.ru *.eaglecdn.com event.top100.su export-download.canva.com ext.clickstream.sberbank.ru sdk.canva.com *.g.doubleclick.net googleads.g.doubleclick.net *.google-analytics.com *.googleapis.com *.google.com google.com *.googletagmanager.com googletagmanager.com graph.facebook.com gstatic.com id.sber.ru *.lj.ru lj.stat.eagleplatform.com mc.yandex.by mc.yandex.com mc.yandex.md mc.yandex.ru pingback.giphy.com *.pingdom.net privacy-cs.mail.ru *.rambler-co.ru rambler-co.ru *.rambler.ru rambler.ru rb.infox.sg *.rnet.plus *.services.livejournal.com *.ssp.rambler.ru ssp.rambler.ru static-mon.yandex.net static.xx.fbcdn.net stat.media stats.g.doubleclick.net smi2.net smi2.ru sve.online.sberbank.ru *.tiktok.com tiktok.com top-fwz1.mail.ru *.twitter.com *.webturn.ru *.webvisor.org wss://mc.yandex.ru wss://www.livejournal.com yandexmetrica.com yandexmetrica.com:29010 yandexmetrica.com:30103 *.yandex.net *.yandex.ru yandex.ru yastatic.net ymetrica1.com ymetrica.com *.youtube.com youtube.com". The action has been blocked. |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Content security policy |
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.
Performance issues directly impact user engagement and conversion rates.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| www.livejournal.com/support/faq/350.html | here |
| www.livejournal.com/shop/commpromo.bml | here |
| www.livejournal.com/support/faq/373.html | here |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
span.entryunit__author > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead span.entryunit__author > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead li.b-topten-item > span.ljuser > a.i-ljuser-profile > img.i-ljuser-userhead |
Format your HTML in a way that enables crawlers to better understand your app’s content.
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
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
Mark entry as readMark entry as unr… div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link |
Hide authorBring author back div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link |
div.ng-isolate-scope > div.b-ljpromo > div.b-ljpromo-container > a.b-ljpromo-nav |
div.ng-isolate-scope > div.b-ljpromo > div.b-ljpromo-container > a.b-ljpromo-nav |
Mark entry as readMark entry as unr… div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link |
Hide authorBring author back div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link |
div.ng-isolate-scope > div.b-ljpromo > div.b-ljpromo-container > a.b-ljpromo-nav |
div.ng-isolate-scope > div.b-ljpromo > div.b-ljpromo-container > a.b-ljpromo-nav |
Show New Entries div.l-flatslide-wrapper > div.l-flatslide-content > p.b-mainpage-uprating > a.b-mainpage-uprating-inner |
div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link |
div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link div.entryunit__controls > ul.controls-entryunit__items > li.controls-entryunit__item > a.controls-entryunit__link |
TODAY header.b-topten-head > ul.b-topten-switcher > li.b-topten-switcher-item > a.b-pseudo |
ALL TIME header.b-topten-head > ul.b-topten-switcher > li.b-topten-switcher-item > a.b-pseudo |
TODAY header.b-topten-head > ul.b-topten-switcher > li.b-topten-switcher-item > a.b-pseudo |
ALL TIME header.b-topten-head > ul.b-topten-switcher > li.b-topten-switcher-item > a.b-pseudo |
Skip footer.b-helptour-footer > ul.b-helptour-controls > li.b-helptour-control > a.b-helptour-skip-link |
Prev footer.b-helptour-footer > ul.b-helptour-controls > li.b-helptour-control > a.b-helptour-prev-link |
Next footer.b-helptour-footer > ul.b-helptour-controls > li.b-helptour-control > a.b-helptour-next-link |
Done footer.b-helptour-footer > ul.b-helptour-controls > li.b-helptour-control > a.b-helptour-done-link |
Hide multiple posts from the same account ul.b-mainpage-settings > li.b-mainpage-settings-item > span.b-mainpage-settings-different > a.b-pseudo |
Show multiple posts from the same account ul.b-mainpage-settings > li.b-mainpage-settings-item > span.b-mainpage-settings-different > a.b-pseudo |
Hide posts from friends ul.b-mainpage-settings > li.b-mainpage-settings-item > span.b-mainpage-settings-friends > a.b-pseudo |
Show posts from friends ul.b-mainpage-settings > li.b-mainpage-settings-item > span.b-mainpage-settings-friends > a.b-pseudo |
Hide read posts & blocked usersHide back hidden posts from rating ul.b-mainpage-settings > li.b-mainpage-settings-item > span.b-mainpage-settings-hidden > a.b-pseudo |
Show hidden postsShow hidden posts in rating ul.b-mainpage-settings > li.b-mainpage-settings-item > span.b-mainpage-settings-hidden > a.b-pseudo |
To appear in search results, crawlers need access to your app.
Send Feedback