Tools & Wizards About Us
lololo.ru screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

Page Load Speed

9.5 sec in total

First Response

1.7 sec

Resources Loaded

7.1 sec

Page Rendered

803 ms

lololo.ru screenshot

About Website

Welcome to lololo.ru homepage info - get ready to check Lololo best content for Russia right away, or after learning these important things about lololo.ru

Visit lololo.ru

Key Findings

We analyzed Lololo.ru page load time and found that the first response time was 1.7 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

lololo.ru performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

74/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

lololo.ru

1656 ms

menu.js

826 ms

lol_ajax.js

358 ms

js_edit.js

378 ms

vp.js

493 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 28% of them (22 requests) were addressed to the original Lololo.ru, 17% (13 requests) were made to Vk.com and 9% (7 requests) were made to Bzlwe.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Lololo.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 402.5 kB (43%)

Content Size

931.9 kB

After Optimization

529.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lololo.ru main page is 931.9 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. 35% of websites need less resources to load. Images take 403.8 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 101.1 kB

  • Original 116.2 kB
  • After minification 115.0 kB
  • After compression 15.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 101.1 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 6.7 kB

  • Original 403.8 kB
  • After minification 397.0 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. Lololo images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 246.6 kB

  • Original 352.2 kB
  • After minification 292.9 kB
  • After compression 105.6 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 246.6 kB or 70% of the original size.

CSS Optimization

-81%

Potential reduce by 48.0 kB

  • Original 59.6 kB
  • After minification 47.5 kB
  • After compression 11.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. Lololo.ru needs all CSS files to be minified and compressed as it can save up to 48.0 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (51%)

Requests Now

69

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lololo.ru

lololo.ru

1656 ms

menu.js

menu.js

826 ms

lol_ajax.js

lol_ajax.js

358 ms

js_edit.js

js_edit.js

378 ms

vp.js

vp.js

493 ms

openapi.js

openapi.js

559 ms

a090d438830e2a.js

a090d438830e2a.js

524 ms

bcc55688b.js

bcc55688b.js

492 ms

share.js

share.js

504 ms

cde6dc.js

cde6dc.js

421 ms

top100.jcn

top100.jcn

541 ms

style.css

style.css

1121 ms

basis.css

basis.css

473 ms

highslide.css

highslide.css

267 ms

image-11837.jpg

image-11837.jpg

1260 ms

image-32615.jpg

image-32615.jpg

3560 ms

loading.gif

loading.gif

371 ms

lololo.gif

lololo.gif

668 ms

search.jpg

search.jpg

367 ms

icon.gif

icon.gif

375 ms

18.png

18.png

489 ms

h_fon.jpg

h_fon.jpg

355 ms

hd_f.jpg

hd_f.jpg

353 ms

tbut_on.jpg

tbut_on.jpg

667 ms

upload.gif

upload.gif

744 ms

widget_community.php

widget_community.php

1181 ms

jquery.js

jquery.js

650 ms

657 ms

title_rvf.jpg

title_rvf.jpg

615 ms

rating.gif

rating.gif

598 ms

title_rvfr.jpg

title_rvfr.jpg

575 ms

716 ms

f-fut.jpg

f-fut.jpg

572 ms

hit

hit

409 ms

top100.scn

top100.scn

212 ms

watch.js

watch.js

34 ms

b-share-form-button.png

b-share-form-button.png

179 ms

watch.js

watch.js

16 ms

b-share-form-button_share__icon.png

b-share-form-button_share__icon.png

211 ms

b-share-icon.png

b-share-icon.png

247 ms

b-share-popup_down__tail.png

b-share-popup_down__tail.png

248 ms

669725.js

669725.js

338 ms

669726.js

669726.js

361 ms

loader_nav19239_3.js

loader_nav19239_3.js

334 ms

lite.css

lite.css

340 ms

lite.js

lite.js

700 ms

lang3_0.js

lang3_0.js

332 ms

widget_community.css

widget_community.css

334 ms

xdm.js

xdm.js

348 ms

al_community.js

al_community.js

488 ms

669725.html

669725.html

154 ms

669726.html

669726.html

151 ms

jQuery.js

jQuery.js

118 ms

zoom.js

zoom.js

246 ms

jQuery.js

jQuery.js

123 ms

zoom.js

zoom.js

242 ms

jsonp.php

jsonp.php

201 ms

jsonp.php

jsonp.php

226 ms

180x180.gif

180x180.gif

459 ms

180x180.gif

180x180.gif

1399 ms

180x180.gif

180x180.gif

198 ms

170x170.gif

170x170.gif

497 ms

170x170.gif

170x170.gif

268 ms

170x170.gif

170x170.gif

1233 ms

d-YEHkFUvVs.jpg

d-YEHkFUvVs.jpg

452 ms

xhe43G0arTE.jpg

xhe43G0arTE.jpg

361 ms

9dtoNduqnOI.jpg

9dtoNduqnOI.jpg

473 ms

tcOF2gzhVpo.jpg

tcOF2gzhVpo.jpg

473 ms

B7sCNJZ0Has.jpg

B7sCNJZ0Has.jpg

332 ms

NEywK0v6-Ug.jpg

NEywK0v6-Ug.jpg

455 ms

s9xEPuDgLv0.jpg

s9xEPuDgLv0.jpg

450 ms

1K-h7ZhMoBs.jpg

1K-h7ZhMoBs.jpg

1061 ms

hkk9AQilJmI.jpg

hkk9AQilJmI.jpg

344 ms

xYEaUElT-z0.jpg

xYEaUElT-z0.jpg

517 ms

Jo8Ax27J4h8.jpg

Jo8Ax27J4h8.jpg

479 ms

camera_50.png

camera_50.png

159 ms

deactivated_50.png

deactivated_50.png

159 ms

w_logo.png

w_logo.png

145 ms

Accessibility Review

lololo.ru accessibility score

70

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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.

Impact

Issue

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Internationalization and localization

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

Impact

Issue

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lololo.ru best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

lololo.ru SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Mobile Friendly

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/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lololo.ru can be misinterpreted by Google and other search engines. Our service has detected that English 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 Lololo.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

lololo.ru

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