Access corpus.ru. Российская и зарубежная литература | Качественные книги для взыскательного читателя

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value21.7 s

0/100

25%

SI (Speed Index)

Value16.6 s

0/100

10%

TBT (Total Blocking Time)

Value2,140 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

corpus.ru

557 ms

www.corpus.ru

1358 ms

bootstrap.css

155 ms

style.css

311 ms

jquery.fancybox.min.css

35 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 86% of them (78 requests) were addressed to the original Corpus.ru, 3% (3 requests) were made to Maxcdn.bootstrapcdn.com and 2% (2 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Corpus.ru.

Content Size

1.7 MB

After Optimization

1.6 MB

In fact, the total size of Corpus.ru main page is 1.7 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. 65% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 123.0 kB

Original 139.0 kB
After minification 104.6 kB
After compression 16.0 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. This page needs HTML code to be minified as it can gain 34.4 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 123.0 kB or 89% of the original size.

Image Optimization

-2%

Potential reduce by 27.0 kB

Original 1.4 MB
After minification 1.4 MB

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. Corpus images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

Original 130.6 kB
After minification 130.6 kB
After compression 128.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. This website has mostly compressed JavaScripts.

CSS Optimization

-8%

Potential reduce by 3.6 kB

Original 44.6 kB
After minification 44.6 kB
After compression 41.1 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. Corpus.ru has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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 the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Form elements do not have associated labels

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

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

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

Search Engine Optimization Advices

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

RU
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Corpus.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Corpus.ru 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

corpus.ru

Open Graph data is detected on the main page of Corpus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Российская и зарубежная литература | Качественные книги для взыскательного читателя

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

corpus.ru

www.corpus.ru

bootstrap.css

style.css

jquery.fancybox.min.css

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

corpus.ru

www.corpus.ru

bootstrap.css

style.css

jquery.fancybox.min.css

font-awesome.min.css

slick.css

star-rating.css

jquery-1.12.4.min.js

bootstrap.min.js

jquery.form.min.js

jquery.adrecom.form.valid.min.js

svg4everybody.min.js

slick.min.js

jquery.fancybox.min.js

star-rating.min.js

theme.min.js

script.js

css

gtm.js

tag.js

fbevents.js

logo.svg

sprite.svg

tnw160-cover1-partasarati.jpg

tnw160-kiper-stranniki.jpg

tnw160-cover1-skytaltsy.jpg

tnw160-cover-hvatit-pro-lubov.jpg

tnw160-cover1-rushdie-dom.jpg

tnw160-cover1-gari-zmei.jpg

tnw160-cover1-bibliotekarist.jpg

tnw160-cover1-motova-new.jpg

tnw160-cover1-lomonosov.jpg

tnw160-cover1-poryadok.jpg

tnw160-cover1-pod-rozami.jpg

tnw160-cover1-ward-poite.jpg

tnw160-cover1-ne-samoe-glavnoe.jpg

tnw160-cover1-havier-marias.jpg

tnw160-cover1-kurukin-istor.jpg

tnw160-cover1-joseph-anton.jpg

tnw160-cover1-morn.jpg

tnw160-cover-ten-bogov.jpg

tnw160-cover1-harms.jpg