Access fritzmorgen.livejournal.com. Место для дискуссий

name

value

score

weighting

FCP (First Contentful Paint)

Value8.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value30.0 s

0/100

25%

SI (Speed Index)

Value22.4 s

0/100

10%

TBT (Total Blocking Time)

Value4,900 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.328

35/100

15%

TTI (Time to Interactive)

Value32.4 s

0/100

10%

fritzmorgen.livejournal.com

602 ms

l-stat.livejournal.net

11 ms

l-stat.livejournal.net

21 ms

l-stat.livejournal.net

38 ms

19 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 Fritzmorgen.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 (642 ms) relates to the external source Mc.yandex.ru.

Content Size

2.6 MB

After Optimization

1.0 MB

In fact, the total size of Fritzmorgen.livejournal.com main page is 2.6 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 135.0 kB

Original 194.4 kB
After minification 180.3 kB
After compression 59.4 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 135.0 kB or 69% of the original size.

Image Optimization

-8%

Potential reduce by 1.3 kB

Original 16.2 kB
After minification 14.9 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. Fritzmorgen Live Journal images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 913.2 kB

Original 1.4 MB
After minification 1.3 MB
After compression 464.0 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 913.2 kB or 66% of the original size.

CSS Optimization

-53%

Potential reduce by 539.7 kB

Original 1.0 MB
After minification 1.0 MB
After compression 469.6 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. Fritzmorgen.livejournal.com needs all CSS files to be minified and compressed as it can save up to 539.7 kB or 53% of the original size.

Requests Now

After Optimization

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

High

Registers an unload listener

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

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

fritzmorgen.livejournal.com

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

fritzmorgen.livejournal.com

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

fritzmorgen.livejournal.com

l-stat.livejournal.net

l-stat.livejournal.net

l-stat.livejournal.net

top100.js

yandex_metrika.js

rta.js

analytics.js

beacon.js

gtm.js

autocontext2_async.js

12791732

330412_original.jpg

l.lj-toys.com

l.lj-toys.com

dc.js

green2.min.js

xtcore.js

330231_original.jpg

329958_original.jpg

329566_original.png

327177_original.jpg

326770_original.png

326522_original.png

326358_original.png

logo.svg

s-icons.svg

userinfo_v3.svg

userinfo.gif

print-logo.png

CaMCUg==

6iMf6F5oPfgFuPAEB

QRzzWv9J88AsQYwKv

watch.js

rVlhMGQgDkY

qij_kttWFUo

emily

begun.html

__utm.gif

emily

emily

autocontext2_async.js

top100.scn

ban.ban