13.3 sec in total
836 ms
12 sec
451 ms
Click here to check amazing Alexkosh content for Russia. Otherwise, check out these important facts you probably never knew about alexkosh.ru
Официальный сайт писателя Алекса Коша: новости о выходе книг, блог, отрывки новых книг, продажа книг.
Visit alexkosh.ruWe analyzed Alexkosh.ru page load time and found that the first response time was 836 ms and then it took 12.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
alexkosh.ru performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value11.8 s
0/100
25%
Value17.8 s
0/100
10%
Value1,040 ms
26/100
30%
Value0.007
100/100
15%
Value59.0 s
0/100
10%
836 ms
134 ms
265 ms
262 ms
269 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 87% of them (83 requests) were addressed to the original Alexkosh.ru, 3% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (9.9 sec) relates to the external source Mc.yandex.ru.
Page size can be reduced by 1.1 MB (30%)
3.5 MB
2.5 MB
In fact, the total size of Alexkosh.ru main page is 3.5 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 38.6 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 6.1 kB, which is 12% 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 38.6 kB or 79% of the original size.
Potential reduce by 44.7 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. Alexkosh images are well optimized though.
Potential reduce by 840.7 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 840.7 kB or 73% of the original size.
Potential reduce by 142.7 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. Alexkosh.ru needs all CSS files to be minified and compressed as it can save up to 142.7 kB or 86% of the original size.
Number of requests can be reduced by 37 (41%)
90
53
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alexkosh. 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 16 to 1 for CSS and as a result speed up the page load time.
alexkosh.ru
836 ms
style.css
134 ms
jcemediabox.css
265 ms
style.css
262 ms
modal.css
269 ms
btcontentslider.css
265 ms
layerslider.css
266 ms
layerslider.transitiongallery.css
269 ms
imagelightbox.css
407 ms
mootools-core.js
536 ms
core.js
408 ms
mootools-more.js
807 ms
scrolltotop_mt.js
408 ms
jquery.min.js
532 ms
jquery-noconflict.js
562 ms
jquery-migrate.min.js
562 ms
caption.js
561 ms
jcemediabox.js
678 ms
modal.js
670 ms
slides.js
669 ms
default.js
669 ms
jquery.easing.1.3.js
672 ms
layerslider.kreaturamedia.jquery.js
942 ms
layerslider.transitions.js
878 ms
TweenMax.min.js
348 ms
layerslider.transition.gallery.js
876 ms
jquery.minicolors.js
878 ms
imagelightbox.js
878 ms
css
72 ms
system.css
934 ms
general.css
974 ms
k2.css
976 ms
style.css
981 ms
css
45 ms
api.js
56 ms
system.css
199 ms
recaptcha__en.js
120 ms
topback3.jpg
392 ms
dragon2.png
650 ms
login.png
171 ms
blank.gif
170 ms
74807b17b16592d9083e5c626866e844-of_full_book.png
392 ms
18d49fa78cd18ba9217f107edb937f82-o1_book.png
383 ms
0e9a7eafdccc361b2bfca9729af87e1e-book_in_progress.png
265 ms
a98ddbf30750e6304858dee771c17dd1-op_book.png
784 ms
54927b26d72be53b90e894920808f49e-eyabv_book2.png
773 ms
5aaf7570b9349eaf0c416e7faf179cf4-nnn_book.png
677 ms
0dc9ef75dc3c9e28d21d1c40ce60b139-vvv_book1.png
648 ms
1194fe42e94c98330904527b054ce04e-ol_book.png
653 ms
d13c4f44e9d6a5169a1d33468e312286-of_en_book.png
2044 ms
aaef3ed80c9e9ea1214ccff34b8934db-vvv_book2.png
904 ms
6efc2d6d5e2dbe359772e67df2fd4d29-eyabv_book1.png
2171 ms
e6a299f1b198dcf1aebd072ae7110a92-of_book.png
2032 ms
7c2511c55addfce29630b38a9224efee-book_in_plans.png
1658 ms
8de42645b7637593b9deec115c834349-oo_book.png
2175 ms
0ec379d156af402c7dd64609ee29bf81-im_book.png
2030 ms
939ba915465ba7ed7c44a47bdfc7d45d-mi_book.png
2287 ms
XPIqWfaT1iI.jpg
2544 ms
01.jpg
2165 ms
02.jpg
2177 ms
03.jpg
2295 ms
04.jpg
2303 ms
vk.png
2320 ms
facebook.png
2309 ms
instagram.png
2418 ms
twitter.png
2425 ms
livejournal.png
2436 ms
rss.png
2442 ms
menuback2.png
2571 ms
bg.jpg
2662 ms
nBF2d6Y3AbOwfkBM-9HcWKCWcynf_cDxXwCLxiixG1c.ttf
94 ms
qwCYE106NwHxtQIaygqBug.ttf
94 ms
4z2U46_RRLOfkoHsWJG3v6CWcynf_cDxXwCLxiixG1c.ttf
144 ms
alexkosh-webfont.woff
2535 ms
rzd3.png
2543 ms
title-rec.png
2549 ms
watch.js
9870 ms
analytics.js
61 ms
collect
30 ms
skin.css
2509 ms
popup.html
2521 ms
tooltip.html
2443 ms
jc_blog.gif
2330 ms
bg_f.png
2981 ms
copyr1.png
2427 ms
button-up.png
2163 ms
re-left.png
2170 ms
re-right.png
2187 ms
loading.gif
2171 ms
pagination.png
2167 ms
counter
268 ms
blank.gif
1802 ms
block.png
1799 ms
skin1.png
306 ms
loading.gif
306 ms
alexkosh.ru accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
alexkosh.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
alexkosh.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alexkosh.ru 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 Alexkosh.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.
alexkosh.ru
Open Graph description is not detected on the main page of Alexkosh. 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: