Access rojkov.livejournal.com. За Мир! Бредни престарелого ролевика

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value34.0 s

0/100

25%

SI (Speed Index)

Value21.7 s

0/100

10%

TBT (Total Blocking Time)

Value2,630 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.328

35/100

15%

TTI (Time to Interactive)

Value32.1 s

0/100

10%

rojkov.livejournal.com

1097 ms

analytics.js

40 ms

l-stat.livejournal.net

10 ms

l-stat.livejournal.net

19 ms

l-stat.livejournal.net

43 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rojkov.livejournal.com, 12% (13 requests) were made to L-stat.livejournal.net and 9% (10 requests) were made to Ssp.rambler.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Api.plus1.wapstart.ru.

Content Size

2.4 MB

After Optimization

979.9 kB

In fact, the total size of Rojkov.livejournal.com main page is 2.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 170.4 kB

Original 239.5 kB
After minification 225.5 kB
After compression 69.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 170.4 kB or 71% of the original size.

Image Optimization

-2%

Potential reduce by 1.0 kB

Original 45.2 kB
After minification 44.2 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Rojkov Live Journal images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 903.3 kB

Original 1.3 MB
After minification 1.3 MB
After compression 437.8 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 903.3 kB or 67% of the original size.

CSS Optimization

-44%

Potential reduce by 342.2 kB

Original 771.1 kB
After minification 768.7 kB
After compression 428.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Rojkov.livejournal.com needs all CSS files to be minified and compressed as it can save up to 342.2 kB or 44% of the original size.

Requests Now

After Optimization

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rojkov Live Journal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

RU
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rojkov.livejournal.com can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Rojkov.livejournal.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

rojkov.livejournal.com

Open Graph description is not detected on the main page of Rojkov Live Journal. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks:

Report Summary

Performance

Accessibility

Best Practices

SEO

За Мир! Бредни престарелого ролевика — LiveJournal

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

rojkov.livejournal.com

analytics.js

l-stat.livejournal.net

l-stat.livejournal.net

l-stat.livejournal.net

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

rojkov.livejournal.com

analytics.js

l-stat.livejournal.net

l-stat.livejournal.net

l-stat.livejournal.net

top100.js

yandex_metrika.js

rta.js

beacon.js

gtm.js

autocontext2_async.js

5382721

xtcore.js

logo.svg

s-icons.svg

userinfo_v3.svg

userinfo.gif

print-logo.png

CaMCUg==

6iMf6F5oPfgFuPAEB

watch.js

QRzzWv9J88AsQYwKv

green2.min.js

emily

begun.html

emily

001001.gif

top100.scn

gpt.js

emily

autocontext2_async.js

watch.js

pubads_impl_82.js

container.html

autocontext2.js

ads

ban.ban

12328.js

osd.js

collect

collect

collect

autocontext2.js