6.2 sec in total
514 ms
5.4 sec
314 ms
Welcome to paleo.ru homepage info - get ready to check Paleo best content for Russia right away, or after learning these important things about paleo.ru
Палеонтологический институт РАН
Visit paleo.ruWe analyzed Paleo.ru page load time and found that the first response time was 514 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
paleo.ru performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value10.5 s
0/100
25%
Value12.8 s
2/100
10%
Value220 ms
88/100
30%
Value0.245
51/100
15%
Value15.7 s
6/100
10%
514 ms
517 ms
924 ms
254 ms
368 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 93% of them (66 requests) were addressed to the original Paleo.ru, 3% (2 requests) were made to Bitrix.info and 3% (2 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Paleo.ru.
Page size can be reduced by 996.7 kB (41%)
2.5 MB
1.5 MB
In fact, the total size of Paleo.ru main page is 2.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. 35% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 33.1 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 5.9 kB, which is 14% 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 33.1 kB or 79% of the original size.
Potential reduce by 71.4 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. Paleo images are well optimized though.
Potential reduce by 849.9 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 849.9 kB or 69% of the original size.
Potential reduce by 42.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. Paleo.ru needs all CSS files to be minified and compressed as it can save up to 42.2 kB or 80% of the original size.
Number of requests can be reduced by 28 (42%)
67
39
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Paleo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
paleo.ru
514 ms
www.paleo.ru
517 ms
www.paleo.ru
924 ms
style.css
254 ms
style.css
368 ms
style.css
378 ms
style.css
380 ms
core.min.js
1012 ms
kernel_main_v1.js
900 ms
dexie3.bundle.min.js
652 ms
core_ls.min.js
496 ms
core_frame_cache.min.js
501 ms
template_d22a79c713794ff1f4c8c902213e6d82_v1.js
505 ms
main_style.css
734 ms
jquery.fancybox.css
627 ms
jquery.fancybox-thumbs.css
631 ms
skin.css
752 ms
jquery-1.7.2.min.js
888 ms
cufon-yui.js
780 ms
Droid_Sans_400-Droid_Sans_700.font.js
1591 ms
jquery.fancybox.js
879 ms
jquery.mousewheel-3.0.6.pack.js
910 ms
jquery.fancybox-thumbs.js
1005 ms
jquery.jcarousel.js
1051 ms
PIE.js
1052 ms
ba.js
282 ms
body.gif
129 ms
main.jpg
244 ms
header.jpg
379 ms
logo.png
131 ms
sname.png
133 ms
lupa.gif
131 ms
flag_rus_1.png
255 ms
flag_en.png
259 ms
w_dot.png
260 ms
main_in.png
258 ms
museum_enter.jpg
368 ms
%D0%B2%D0%B8%D0%B4%20%D0%BC%D1%83%D0%B7%D0%B5%D1%8F%20-1.jpg
510 ms
%D0%B0%D0%BC%D0%BC%D0%BE%D0%BD%D0%B8%D1%82.jpg
511 ms
04%20Flerov%2BEglon.jpg
515 ms
%D0%AD%D0%BB%D0%B5%D0%BA%D1%82%D1%80%D0%BE%D0%BD%D0%BD%D1%8B%D0%B9%20%D0%BC%D0%B8%D0%BA%D1%80%D0%BE%D1%81%D0%BA%D0%BE%D0%BF.jpg
518 ms
Panorama-mus-winter-prev.jpg
490 ms
%D0%AD%D0%BA%D1%81%D0%BF%D0%B5%D0%B4%D0%B8%D1%86%D0%B8%D1%8F-2-sm.jpg
504 ms
%D0%9E%D1%81%D0%BD%D0%BE%D0%B2%D1%8B-%D1%81%D0%B0%D0%B9%D1%82.JPG
614 ms
%D0%B4%D0%B5%D1%82%20%D1%80%D0%B8%D1%81%D1%83%D0%BD%D0%BE%D0%BA.jpg
633 ms
03%20Borisiak%201933.jpg
639 ms
Montazh%20skeleta%20v%20Kazani.jpg
639 ms
PIN_Poisk_52_opt.jpg
771 ms
%D0%9F%D0%BE%D0%BB%D0%B5%20Madygen_Kirgizi%D0%B0.jpg
648 ms
1948-%D0%9C%D0%BE%D0%BD%D0%B3%D0%BE%D0%BB%D0%B8%D1%8F__%D0%95%D1%84%D1%80%D0%B5%D0%BC%D0%BE%D0%B2_%D0%9D%D1%8D%D0%BC%D1%8D%D0%B3%D1%8D%D1%82%D1%83-sm.jpg
738 ms
%D0%9A%D1%83%D1%80%D0%BE%D1%87%D0%BA%D0%B8%D0%BD%20%D0%98%D0%B2%D0%B0%D1%85%D0%BD%D0%B5%D0%BD%D0%BA%D0%BE%20-sm.jpg
760 ms
Boryssiak_.jpg
767 ms
PIN%20RAS.jpg
766 ms
%D0%A0%D0%B5%D0%BA%D0%BE%D0%BD%D1%81%D1%82%D1%80%D1%83%D0%BA%D1%86%D0%B8%D1%8F%D0%9C%D0%BE%D0%B7%D0%B3%D0%B0%D0%A2%D0%B0%D1%80%D0%B1%D0%BE%D0%B7%D0%B0%D0%B2%D1%80%D0%B0%D0%98%20%D0%B5%D0%B3%D0%BE%D0%A7%D0%B5%D1%80%D0%B5%D0%BF.jpg
778 ms
1949%D0%9E%D1%80%D0%BB%D0%BE%D0%B2%20%D0%B2%D0%B5%D0%B4%D0%B5%D1%82%20%D1%8D%D0%BA%D1%81%D0%BA%D1%83%D1%80%D1%81.jpg
861 ms
%D0%A8%D0%BA%D0%BE%D0%BB%D0%B0-%D1%81%D0%B0%D0%B9%D1%82.JPG
887 ms
%D0%BA%D0%B5%D1%80%D0%B0%D0%BC%20%D0%BF%D0%B0%D0%BD%D0%BD%D0%BE-%D1%81%D0%B0%D0%B9%D1%82.jpg
894 ms
icons.png
894 ms
d87j9rmlbxl278eaokwrmma608tn1x8c.png
899 ms
k3vz15p0bya6esb9k26sciyev6bru985.jpg
1309 ms
v4ehov04landai5vr3gng9rcge1tnxe4.png
984 ms
tag.js
894 ms
a3kq4kkzei8bxgyu8xsnycjxfpfwuwq3.png
1118 ms
bx_stat
187 ms
piwik.js
903 ms
footer.jpg
897 ms
prev-horizontal.png
913 ms
next-horizontal.png
980 ms
advert.gif
627 ms
piwik.php
910 ms
1
144 ms
paleo.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.
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
paleo.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
paleo.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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Paleo.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 Paleo.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.
paleo.ru
Open Graph description is not detected on the main page of Paleo. 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: