13.8 sec in total
1.3 sec
10.1 sec
2.3 sec
Click here to check amazing Planscan content for Russia. Otherwise, check out these important facts you probably never knew about planscan.ru
Книжные сканеры ЭларСкан - семейство универсальных сканеров планетарного типа для сканирования разноформатных документов, любых книг и папок, сброшюрованных, "сложных", ветхих или поврежденных докумен...
Visit planscan.ruWe analyzed Planscan.ru page load time and found that the first response time was 1.3 sec and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
planscan.ru performance score
name
value
score
weighting
Value21.9 s
0/100
10%
Value33.5 s
0/100
25%
Value25.6 s
0/100
10%
Value480 ms
60/100
30%
Value0.001
100/100
15%
Value27.8 s
0/100
10%
1290 ms
1203 ms
374 ms
753 ms
528 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Planscan.ru, 80% (85 requests) were made to Elarscan.ru and 8% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Elarscan.ru.
Page size can be reduced by 1.5 MB (35%)
4.3 MB
2.8 MB
In fact, the total size of Planscan.ru main page is 4.3 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.3 MB which makes up the majority of the site volume.
Potential reduce by 68.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. This page needs HTML code to be minified as it can gain 25.3 kB, which is 31% 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 68.4 kB or 84% of the original size.
Potential reduce by 122.3 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. Planscan images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 64% of the original size.
Potential reduce by 205.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. Planscan.ru needs all CSS files to be minified and compressed as it can save up to 205.1 kB or 86% of the original size.
Number of requests can be reduced by 47 (49%)
95
48
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Planscan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
planscan.ru
1290 ms
elarscan.ru
1203 ms
custom.css
374 ms
common-styles.css
753 ms
home.css
528 ms
jquery.mCustomScrollbar.min.css
787 ms
jquery.fancybox.min.css
516 ms
fancybox-custom.css
525 ms
swiper.min.css
748 ms
home-slider.css
897 ms
swiper-custom.css
898 ms
home-adv.css
912 ms
home-news-list.css
1120 ms
home-info.css
1123 ms
core.js
1797 ms
protobuf.js
1771 ms
model.js
1531 ms
rest.client.js
1409 ms
pull.client.js
1752 ms
jquery-3.2.1.min.js
1752 ms
jquery-migrate-3.2.0.min.js
1791 ms
modernizr-custom.js
1903 ms
jquery.selectric.js
2255 ms
jquery.selectric.placeholder.js
2132 ms
jquery.maskedinput.min.js
2144 ms
common.js
2171 ms
custom.js
2172 ms
script.js
2283 ms
swiper.min.js
3002 ms
jquery.mCustomScrollbar.min.js
2650 ms
jquery.mousewheel.min.js
2551 ms
jquery.fancybox.min.js
2792 ms
script.js
2634 ms
script.js
2663 ms
script.js
2925 ms
css2
52 ms
css2
69 ms
js
70 ms
api.js
48 ms
jquery.mousewheel.min.js
143 ms
ba.js
359 ms
tag.js
1043 ms
header-logo.svg
474 ms
header-nav-button.svg
468 ms
header-logo-white.svg
464 ms
zen.svg
465 ms
vk.svg
463 ms
rutube.svg
460 ms
nav-animate-1.png
969 ms
nav-animate-2.png
1124 ms
ddagg7vh6y8tjubus2jymvzd8hqsvkvx.png
847 ms
q8exkbxzi6s9v5vapbkda10r4pld9rds.png
847 ms
6f7az2k2p87zmbf5dk8p9p0zemhr5jb9.png
845 ms
lrmvtuur8c1qpoysbk9fkolaam25mbrl.png
850 ms
m4n9c6d6mh07w7hk3qgqlgjw92y31avz.png
1230 ms
7zl51kkjkbp761dhd51yz1yyjdbt3nxr.jpg
1227 ms
bullet-home-slider.svg
1229 ms
jkes0qs7r0ywkhawtdtjr47rztpmpp1c.png
1228 ms
7tqeyarr81z5qg63j3a1r2qkbdwp3y5j.png
1340 ms
jkyorbvm0mrsypwxwgryshxz7axq8imx.png
1495 ms
u83ze2viprxh91cqsbmee8n101qealej.png
1601 ms
3r5imepcx2n4iydhhocc9oxulakmtqy2.png
1608 ms
a6xxemg8u9aj3xxbkyi9t54s5hg3dma2.png
1610 ms
iqr9mvm2z805whk4hav0yac0t9nop4re.png
1609 ms
tbhp36ueymvkbwco4079z42ow8ibgbsf.png
1720 ms
v1nsh3b2sis78jgclq1hkz4ushb3ly6w.png
1875 ms
jhwfxlxw513gsx5zbuz2ct0lf5tx9flx.png
2359 ms
f06jq3wjx2j1tuars6m5skqhfqzhvh48.png
2472 ms
vs96mrewhmwl9362jxuozfxe7u8h5xvp.png
2489 ms
opc50cifl3vjy68sykmo35z1twdomj23.png
2498 ms
wqxn97yonj13ri0yka12cffgjrhu05xl.png
2587 ms
slider-prev.svg
2249 ms
slider-next.svg
2625 ms
slider-info.svg
2731 ms
dx1t1p341u9qbfu9v4mbsss7978vc3za.JPG
3107 ms
98zr8lv9cv7595bsr3tiirj2h58a1tla.jpg
3120 ms
home-more.jpg
3257 ms
home-more-arrow.svg
2895 ms
KFOmCnqEu92Fr1Me5Q.ttf
103 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
123 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
145 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
139 ms
KFOkCnqEu92Fr1Mu52xP.ttf
159 ms
KFOjCnqEu92Fr1Mu51S7ABc9.ttf
160 ms
KFOjCnqEu92Fr1Mu51TjARc9.ttf
159 ms
KFOjCnqEu92Fr1Mu51TzBhc9.ttf
159 ms
recaptcha__en.js
61 ms
bx_stat
185 ms
home-links.jpg
2786 ms
earth.png
3154 ms
1.png
3260 ms
home-info-map.png
3403 ms
3.jpg
3285 ms
f-nav.svg
3151 ms
f-doc.svg
2798 ms
footer-logo-mc.svg
3269 ms
footer-logo-mpt.svg
3158 ms
vf2zlps7rb0hhuj1ile2emljg0f9h3b6.png
3290 ms
j7x30qcy4dz2kbyfe16begssmzj32yuj.png
3267 ms
advert.gif
611 ms
7gx2o078300wwo2qyl3i4uta4s5073l4.png
3136 ms
2vwn4q7ifqyt4lkvjxhfgegm1cdfvhvs.png
3146 ms
c7t4k0cxjqsji2xu304k9enpi4aax6e1.png
3271 ms
9iaqi5m72q540utfe9itwavmkrrp11qw.png
3389 ms
sync_cookie_image_decide
122 ms
1
127 ms
planscan.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.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
planscan.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
Page has valid source maps
planscan.ru SEO score
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Planscan.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 Planscan.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.
planscan.ru
Open Graph description is not detected on the main page of Planscan. 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: