4.9 sec in total
821 ms
3.3 sec
715 ms
Visit eidos.ru now to see the best up-to-date Eidos content for Russia and also check out these interesting facts you probably never knew about eidos.ru
Eidos.Ru > Дистанционное образование: курсы, олимпиады, конкурсы, конференции
Visit eidos.ruWe analyzed Eidos.ru page load time and found that the first response time was 821 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
eidos.ru performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value12.1 s
0/100
25%
Value12.3 s
3/100
10%
Value980 ms
28/100
30%
Value0.199
62/100
15%
Value13.7 s
11/100
10%
821 ms
274 ms
292 ms
392 ms
274 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 95% of them (108 requests) were addressed to the original Eidos.ru, 2% (2 requests) were made to U876.31.spylog.com and 1% (1 request) were made to Market.zakupki.mos.ru. The less responsive or slowest element that took the longest time to load (984 ms) belongs to the original domain Eidos.ru.
Page size can be reduced by 134.8 kB (18%)
761.6 kB
626.8 kB
In fact, the total size of Eidos.ru main page is 761.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 633.7 kB which makes up the majority of the site volume.
Potential reduce by 106.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 20.5 kB, which is 16% 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 106.6 kB or 83% of the original size.
Potential reduce by 28.2 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. Eidos images are well optimized though.
Number of requests can be reduced by 47 (42%)
111
64
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eidos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
eidos.ru
821 ms
top1.gif
274 ms
logo.gif
292 ms
logo_desc.gif
392 ms
top2.gif
274 ms
top3.gif
291 ms
ruson.gif
367 ms
eng.gif
378 ms
120x60_fgos2.jpg
538 ms
ban3-1.gif
402 ms
ban1.gif
394 ms
ban2.gif
496 ms
mid1.gif
508 ms
mid2.gif
518 ms
t1-1.gif
521 ms
t1-2.gif
535 ms
t1-3.gif
621 ms
t1-4.gif
632 ms
t1-5.jpg
646 ms
t1-6.gif
648 ms
t2-7.gif
667 ms
t1-7.gif
667 ms
t1-8.gif
746 ms
t1-9.gif
837 ms
t1-10.gif
774 ms
t1-11.gif
773 ms
t1-12.jpg
797 ms
t1-13.gif
798 ms
eidos-action03.jpg
890 ms
t3-1.gif
908 ms
t3-2.gif
908 ms
t3-3.gif
930 ms
t3-4.gif
938 ms
PortalUser_09.png
652 ms
t3-7.gif
844 ms
t3-8.gif
902 ms
t3-10.gif
916 ms
yamoney_logo88x31.gif
776 ms
top100.cnt
257 ms
mid4.gif
773 ms
mid5.gif
797 ms
mid6.gif
790 ms
mid7.gif
807 ms
mid8-4.gif
870 ms
cnt
619 ms
mid9.gif
825 ms
mid10.gif
818 ms
mid11.gif
837 ms
girl1.gif
868 ms
mid12.gif
850 ms
girl2.gif
812 ms
mid13.gif
813 ms
znaete1.gif
809 ms
znaete2.gif
837 ms
svid5.gif
858 ms
prize2.gif
861 ms
t2-7-1.gif
815 ms
t4-1.gif
820 ms
t4-2.gif
809 ms
ul.gif
842 ms
EidosRu_IMG_2014m.jpg
854 ms
l.gif
862 ms
Eidos_DSC01566_150x150.jpg
822 ms
piter01.jpg
817 ms
koktebel150.jpg
817 ms
Eidos_WP_20160218_0150x150.jpg
827 ms
Eidos_P1090710_150x150.jpg
857 ms
EidosRu_IMG_0024_150.jpg
845 ms
Eidos_Seminar150x150.jpg
806 ms
u876.31.spylog.com
246 ms
dm.gif
818 ms
ny_el.gif
820 ms
EidosRu_IMG_1964-kh.jpg
829 ms
EidosRu_IMG_2795_150.jpg
843 ms
EidosJournal-150.jpg
853 ms
EidosRu_IMG_0017_150x150.jpg
800 ms
matem_1_4a.jpg
954 ms
EidosRu_IMG_1967_150x150.jpg
821 ms
Eidos_Seminar150-4.jpg
832 ms
EidosRu_IMG_9832_150x150.jpg
836 ms
EidosRu_IMG_3614_150x150.jpg
866 ms
cnt
248 ms
oblojka150.jpg
805 ms
reiting.jpg
806 ms
EidosRu_IMG_1357_150x150.jpg
843 ms
doctrina150.jpg
831 ms
consept150.jpg
853 ms
tezaurus150.jpg
839 ms
Metodologaya111.jpg
830 ms
Slovo111.jpg
816 ms
chisla1-111.jpg
984 ms
Meta-Miroved111.jpg
836 ms
meta111.jpg
929 ms
Literat9-11a.jpg
863 ms
russian_language9-11a.jpg
968 ms
eng_1_5a.jpg
823 ms
inform_1_4a.jpg
979 ms
biology_5_11a.jpg
921 ms
wm1.gif
916 ms
qiwi%20gorizontal-mini31.jpg
918 ms
Kvit.png
886 ms
shet.png
940 ms
t1-6-1.gif
954 ms
school01.jpg
939 ms
goldensite.gif
910 ms
laureat88x31-2005.gif
915 ms
internit100x47.gif
886 ms
fb.gif
934 ms
mm.png
957 ms
vk.gif
927 ms
tw.gif
912 ms
youtube.png
890 ms
bot1.gif
903 ms
bot2.gif
927 ms
eidos.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-hidden="true"] elements contain focusable descendents
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
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
eidos.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
eidos.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 Eidos.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 Eidos.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.
eidos.ru
Open Graph description is not detected on the main page of Eidos. 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: