6.1 sec in total
807 ms
4.8 sec
446 ms
Visit pritchi.ru now to see the best up-to-date Pritchi content for Russia and also check out these interesting facts you probably never knew about pritchi.ru
Целью проекта Притчи.ру® является сбор притч всех времён и народов в одном месте, классификация, сортировка и предоставление читателю возможности быстрого поиска притч по названию, тематике и происхож...
Visit pritchi.ruWe analyzed Pritchi.ru page load time and found that the first response time was 807 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
pritchi.ru performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value5.0 s
27/100
25%
Value11.9 s
4/100
10%
Value10,080 ms
0/100
30%
Value0.237
53/100
15%
Value36.9 s
0/100
10%
807 ms
467 ms
237 ms
702 ms
471 ms
Our browser made a total of 184 requests to load all elements on the main page. We found that 34% of them (62 requests) were addressed to the original Pritchi.ru, 8% (15 requests) were made to Ulogin.ru and 7% (12 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Ulogin.ru.
Page size can be reduced by 613.7 kB (60%)
1.0 MB
405.3 kB
In fact, the total size of Pritchi.ru main page is 1.0 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. 55% of websites need less resources to load. Javascripts take 605.9 kB which makes up the majority of the site volume.
Potential reduce by 115.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 115.4 kB or 82% of the original size.
Potential reduce by 21.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. Pritchi images are well optimized though.
Potential reduce by 429.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 429.7 kB or 71% of the original size.
Potential reduce by 47.2 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. Pritchi.ru needs all CSS files to be minified and compressed as it can save up to 47.2 kB or 80% of the original size.
Number of requests can be reduced by 108 (62%)
173
65
The browser has sent 173 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pritchi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
pritchi.ru
807 ms
base.css
467 ms
getKWvars_pub.css
237 ms
jquery.min.js
702 ms
form.js
471 ms
getKWvars.js
351 ms
copy.css
353 ms
copy.js
461 ms
guestLightBoxG.js
470 ms
ulogin.js
541 ms
show.cgi
459 ms
openapi.js
388 ms
informer.php
455 ms
orphus.js
242 ms
table.gif
118 ms
tape_gr.gif
117 ms
tape_gr1.gif
118 ms
right_header.gif
242 ms
logo.gif
123 ms
bmargin11.jpg
119 ms
bgtopbook.gif
241 ms
bm_home_up.gif
241 ms
bm_directory.gif
241 ms
bm_list.gif
241 ms
bm_index.gif
241 ms
bm_rating.gif
357 ms
bm_shop.gif
356 ms
bm_literature.gif
354 ms
spine.gif
356 ms
bgleftbook.gif
356 ms
pattern_b.gif
357 ms
btn_find.gif
472 ms
bullet.gif
440 ms
continue.gif
443 ms
size_small.gif
443 ms
size_medium.gif
444 ms
size_big.gif
444 ms
ico_man.gif
555 ms
topic_read.gif
555 ms
p.gif
555 ms
middlegrad.gif
557 ms
pattern_sy.gif
558 ms
btn_enter.gif
557 ms
count.gif
418 ms
index2.php
300 ms
top100.cnt
386 ms
btn_subscribe.gif
660 ms
cp.gif
660 ms
orphus.gif
669 ms
rss.gif
662 ms
twitter.png
661 ms
livejournal.png
663 ms
facebook.png
775 ms
blank.gif
798 ms
match
184 ms
link.png
811 ms
context.js
223 ms
panel.png
1131 ms
odnoklassniki.png
711 ms
vkontakte.png
709 ms
mmir.png
709 ms
google-plus.png
709 ms
pattern_sw.gif
712 ms
166 ms
context_static_r1065.js
331 ms
5828
147 ms
watch.js
206 ms
y90
10 ms
x90
7 ms
x90
7 ms
context.js
112 ms
watch.js
462 ms
info.min.js
422 ms
10633.js
135 ms
hit;All_da_nnn_dn_realty
258 ms
pixel.gif
198 ms
counter
421 ms
3287582.jpg
564 ms
aci.js
185 ms
bl_shadow_m.gif
119 ms
bl_shadow_l.gif
120 ms
bl_shadow_r.gif
120 ms
upload.gif
132 ms
widget_community.php
287 ms
lb_conor.gif
126 ms
bottom_shadow.gif
125 ms
spineb1.gif
125 ms
spineb2.gif
210 ms
bgleftsheet.gif
213 ms
putme.js
844 ms
hit
260 ms
cnt.js
259 ms
twist_connor.gif
210 ms
bgrightsheet.gif
251 ms
rightsheetconnor.gif
250 ms
stats.html
156 ms
drop.html
163 ms
counter2
159 ms
likebox.php
232 ms
100 ms
194 ms
easyXDM.min.js
166 ms
stats.js
174 ms
iscroll.5.js
174 ms
lang.js
327 ms
drop.js
342 ms
advert.gif
99 ms
1092524.js
164 ms
loader_nav19127_3.js
152 ms
lite.css
152 ms
lite.js
517 ms
lang3_0.js
260 ms
widget_community.css
263 ms
xdm.js
262 ms
al_community.js
261 ms
connect.js
635 ms
jTuqQ-OPDr6.css
53 ms
n370yiaI2G6.css
53 ms
_rx8naC75Dy.js
61 ms
x5F9OMjKyLw.js
59 ms
ICDbTSzjQEg.js
58 ms
TTCre3391I0.js
58 ms
hit
548 ms
272 ms
10414887_865955950110054_2768034845168029737_n.jpg
49 ms
182732_183447775027545_6555088_n.jpg
27 ms
10314726_926690157412989_3818947357292446790_n.jpg
30 ms
10649482_940106286043263_1375277761689694685_n.jpg
29 ms
419425_398415573507528_734224378_n.jpg
32 ms
12651108_213915665621594_7160883698628500929_n.jpg
32 ms
wL6VQj7Ab77.png
18 ms
s7jcwEQH7Sx.png
19 ms
digits
129 ms
cnt
253 ms
1
98 ms
I6-MnjEovm5.js
3 ms
vlXaquuXMrr.js
6 ms
bga.png
153 ms
small.png
159 ms
hit
497 ms
160878
91 ms
match
197 ms
f.gif
133 ms
c_374cf2df.jpg
387 ms
8W3xQ1q9IVQ.jpg
392 ms
mcK3CJ236Jo.jpg
386 ms
psavukCPOzU.jpg
395 ms
_EGobbJY7Bc.jpg
380 ms
q881sc8ajg8.jpg
405 ms
RRHPaVYrIN0.jpg
263 ms
8aw5cVSh13o.jpg
393 ms
1hHeg_Ju2QY.jpg
382 ms
lUfXQZy515g.jpg
396 ms
camera_50.png
129 ms
w_logo.png
127 ms
engine.js
206 ms
dk
168 ms
loadUserData.json
296 ms
widget.a86e7c8a.css
688 ms
image
837 ms
image
827 ms
image
856 ms
image
861 ms
image
790 ms
image
861 ms
image
829 ms
image
861 ms
pixel
26 ms
get.banners.json
110 ms
pixel
17 ms
4jEGR-7BzPu40000gQ00022EktfBRGM5b6m1dh400004klo-QoQmY1B60f6v7jNW3vDKhktYG9ddBwdDiA64b3V1__________yFVmS0=myTt1PK2cm5kGxS2YRRJ7aO3cF__________3ugxQ_Ua0xs-Bcp70wMgT8m6YBYKyv41lAuKNGMc69sbIACKZxRpOtuEdx19xdG5cGoWanOMivYT1Q-L81Mqa5y5sP3F7DgGKmUdWrsekPomZG51iG6oe5800hcbIACKpRnhzwG3phDAl285ql__________3zF__________m_207aJ=6mcSq9K2cm5kGxS2CecSrJAO__________yFYgXLZMYze_NT5wMM1lE8l_csiG6c6fsf8qSLZx7gomGBdxt5KfC1cGQWa1SHhv2c3jcGQXYdZvcejyGUaGP1iG6oe5800hcf8qSLnOyFpQ8wMnFEegFU5zB__________m_J__________yFmW1z4000=YGD_SfK2cm5kGxS2CucHYW6O__________yFYg0FISUzlSih006bgpkm0eYuVwC11Bod6iW2fZ-TeABe2O-ypOEc19-zi6Hx0PaUe9C_5REOIHElbPaFj90f3jcHvHhQa6eOfuzPgBK3kSu2GR41ig1I00AveABe2Ssl3ad7phyKEnK1ql__________3zF__________m_207uI
120 ms
1px-matching-clickganic.gif
273 ms
zr
1012 ms
sync.bumlam.com
491 ms
277726.js
429 ms
cm.gif
317 ms
redot.gif
99 ms
ic_odkl_m.png
160 ms
add-or.png
318 ms
ic_odkl.png
475 ms
showad_full.js
264 ms
1x1.gif
171 ms
adi
276 ms
placeholder.js
87 ms
pritchi.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
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>).
pritchi.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
pritchi.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
RU
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pritchi.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 Pritchi.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.
pritchi.ru
Open Graph description is not detected on the main page of Pritchi. 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: