Access catmotya.livejournal.com. Кот Мотя

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value28.4 s

0/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value4,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.328

35/100

15%

TTI (Time to Interactive)

Value26.4 s

0/100

10%

catmotya.livejournal.com

1163 ms

l-stat.livejournal.net

45 ms

l-stat.livejournal.net

96 ms

l-stat.livejournal.net

56 ms

l-stat.livejournal.net

272 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Catmotya.livejournal.com, 16% (20 requests) were made to L-stat.livejournal.net and 8% (10 requests) were made to Ssp.rambler.ru. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Sync.madnet.ru.

Content Size

630.5 kB

After Optimization

232.8 kB

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

HTML Optimization

-72%

Potential reduce by 156.8 kB

Original 217.0 kB
After minification 198.2 kB
After compression 60.3 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 156.8 kB or 72% of the original size.

Image Optimization

-9%

Potential reduce by 6.1 kB

Original 66.9 kB
After minification 60.8 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. Catmotya Live Journal images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 229.6 kB

Original 339.5 kB
After minification 300.9 kB
After compression 109.9 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 229.6 kB or 68% of the original size.

CSS Optimization

-75%

Potential reduce by 5.3 kB

Original 7.1 kB
After minification 6.6 kB
After compression 1.8 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. Catmotya.livejournal.com needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 75% of the original size.

Requests Now

After Optimization

The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Catmotya 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 38 to 1 for JavaScripts and from 6 to 1 for CSS 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

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Catmotya.livejournal.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Catmotya.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

catmotya.livejournal.com

Open Graph description is not detected on the main page of Catmotya 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

catmotya.livejournal.com

l-stat.livejournal.net

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

catmotya.livejournal.com

l-stat.livejournal.net

l-stat.livejournal.net

l-stat.livejournal.net

l-stat.livejournal.net

screen.css

stylesheet

xtcore.js

analytics.js

rta.js

77261227

18091_900.png

17905_900.png

17650_900.jpg

17240_900.jpg

17147_900.jpg

16786_900.jpg

16611_900.jpg

16246_900.jpg

16009_900.png

15690_900.jpg

userinfo.gif

print-logo.png

data_rss.gif

data_atom.gif

beacon.js

gtm.js

autocontext2_async.js

logo.svg

s-icons.svg

userinfo_v3.svg

header.jpg

content-wt.gif

post-ornament.gif

CaMCUg==

6iMf6F5oPfgFuPAEB

QRzzWv9J88AsQYwKv

top100.js

yandex_metrika.js

autocontext2_async.js

emily

begun.html

watch.js