5.5 sec in total
1.2 sec
3.8 sec
529 ms
Click here to check amazing LOCO content for Russia. Otherwise, check out these important facts you probably never knew about loco.ru
Полезные статьи и уроки по разработке сайтов на различных CMS, фреймворках Yii и CodeIgniter для новичков и опытных разработчиков. Вебстудия LOCO делится своим опытом и ошибками.
Visit loco.ruWe analyzed Loco.ru page load time and found that the first response time was 1.2 sec and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
loco.ru performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value4.0 s
50/100
25%
Value5.3 s
58/100
10%
Value590 ms
50/100
30%
Value0.08
94/100
15%
Value38.3 s
0/100
10%
1241 ms
269 ms
267 ms
677 ms
399 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 77% of them (85 requests) were addressed to the original Loco.ru, 5% (5 requests) were made to Openstat.net and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Loco.ru.
Page size can be reduced by 331.4 kB (19%)
1.7 MB
1.4 MB
In fact, the total size of Loco.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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 67.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 67.3 kB or 78% of the original size.
Potential reduce by 90.5 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. LOCO images are well optimized though.
Potential reduce by 124.4 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 124.4 kB or 60% of the original size.
Potential reduce by 49.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. Loco.ru needs all CSS files to be minified and compressed as it can save up to 49.1 kB or 82% of the original size.
Number of requests can be reduced by 28 (28%)
100
72
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LOCO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
loco.ru
1241 ms
skin.css
269 ms
calendar.css
267 ms
jquery-1.4.2.min.js
677 ms
jquery.jcarousel.min.js
399 ms
mootools.js
548 ms
imageMenu.js
403 ms
scripts.js
516 ms
screen.css
531 ms
form.css
534 ms
main.css
789 ms
imageMenu.css
645 ms
css
22 ms
locoru
57 ms
logo_main.png
217 ms
loco.png
218 ms
sozdanie-saitov.jpg
220 ms
statyi-pro-webrazrabotku.jpg
218 ms
8-esh-plyashi-esh.jpg
357 ms
yii-course-1.png
390 ms
wt_logo.jpg
289 ms
inspire2_logo.png
405 ms
yiico_logo.png
291 ms
rss.jpg
289 ms
02-17-prilipanie-bloka-k-verhu-saita-pri-ego-prokruchivanii.jpg
402 ms
more-button.gif
411 ms
02-08-dzhek-kenfild-mark-viktor-xansen-i-les-xyuitt---celnaya.jpg
418 ms
12-30-anatolii-bukreev-g-becton-de-uolt---voshozhdenie.jpg
484 ms
12-27-dzhoshua-m-grin---zdes-voshodit-solnce.jpg
540 ms
12-27-fedor-konyuhov---sila-very-160-dnei-i-nochei-naedine-s.jpg
573 ms
12-23-interview-katerina-vard.jpg
675 ms
07-09-interview-with-olga-kozar-englishwithexperts.jpg
818 ms
06-21-interview-with-katerina-kozlova-excel-life.jpg
576 ms
11-20-elchin-safarli.png
877 ms
08-04-daniel-kerr.png
805 ms
06-14-etienne-garbugli.jpg
806 ms
06-14-dmitriy-naumenko-codeharmony.jpg
697 ms
06-06-ivan-limanskiy-dj-ivanski-bboy-navy.jpg
949 ms
3_0_FFFFFFFF_E2E2E2FF_0_pageviews
227 ms
2-serdce.jpg
709 ms
corner.png
812 ms
loco_bg_984.png
822 ms
12-30.jpg
830 ms
quotes.gif
849 ms
news_bg-center.jpg
881 ms
news_bg-top.jpg
939 ms
news_bg-bottom.jpg
953 ms
angles.gif
958 ms
author.png
963 ms
comments.gif
980 ms
Vu9Dx8oyiuqEkuIyR3OPDQ.ttf
89 ms
6rYv84POalfstX0SkMI-EvesZW2xOQ-xsNqO47m55DA.ttf
90 ms
content_bg.gif
1017 ms
sergeyratner-krugi-razvitiya-150.jpg
991 ms
yiico-150.jpg
1005 ms
magazindverei1-150.jpg
1007 ms
habibishow-150.jpg
1014 ms
T7MBC_6JTkW2ZBbjf0rXXw.ttf
37 ms
VZ08RdiotRdV1D0ewK-mxC3USBnSvpkopQaUR-2r7iU.ttf
38 ms
watch.js
170 ms
hit
291 ms
sergeyratner-magnit-udachi-150.jpg
964 ms
sergeyratner-voobrajenie-150.jpg
995 ms
cnt.js
249 ms
mps01-150.png
1055 ms
ga.js
29 ms
aci.js
201 ms
__utm.gif
11 ms
sergeyratner-chakry-150.png
1136 ms
sergeyratner-bioenergiya-dvijenie-vpotoke-150.png
1110 ms
profitdoors-150.png
979 ms
pavlovwed-150.png
1122 ms
sergeyratner-podsoznanie-150.png
1136 ms
inspire2-150.png
1068 ms
watch.js
475 ms
webstudio.jpg
1036 ms
101 ms
192 ms
2100769.js
127 ms
photo-video.jpg
1050 ms
design.jpg
1054 ms
arts.jpg
1057 ms
digits
124 ms
cnt
251 ms
articles.jpg
984 ms
286 ms
sites.png
968 ms
logo.png
875 ms
concerts.png
950 ms
photo.png
946 ms
pictures.png
943 ms
presentation.png
917 ms
advert.gif
90 ms
f.gif
125 ms
fitnesspace.jpg
875 ms
infoforum.jpg
878 ms
lgz.png
945 ms
englishow.jpg
951 ms
newsdate.jpg
945 ms
match
190 ms
habibi.png
923 ms
banner-yii-shpargalka-170.jpg
888 ms
banner-opencart-170.png
876 ms
g_plus_icon.jpg
942 ms
twitter_icon.png
951 ms
1
92 ms
prev-horizontal.png
950 ms
next-horizontal.png
926 ms
uZntfDpWSvC-ioDmxvvq5Q
228 ms
print.css
131 ms
loco.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
loco.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
loco.ru SEO score
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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loco.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 Loco.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.
loco.ru
Open Graph description is not detected on the main page of LOCO. 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: