3.9 sec in total
582 ms
2.4 sec
889 ms
Click here to check amazing Orleo content. Otherwise, check out these important facts you probably never knew about orleo.ru
Узнайте больше о наших благотворительных программах, присоединяйтесь к нам и помогите сделать этот мир лучше.
Visit orleo.ruWe analyzed Orleo.ru page load time and found that the first response time was 582 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
orleo.ru performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value3.3 s
70/100
25%
Value4.0 s
81/100
10%
Value230 ms
87/100
30%
Value0
100/100
15%
Value5.9 s
65/100
10%
582 ms
142 ms
266 ms
267 ms
550 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 80% of them (47 requests) were addressed to the original Orleo.ru, 12% (7 requests) were made to Imgs.smartresponder.ru and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (929 ms) relates to the external source Imgs.smartresponder.ru.
Page size can be reduced by 365.0 kB (72%)
507.2 kB
142.1 kB
In fact, the total size of Orleo.ru main page is 507.2 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. 20% of websites need less resources to load. Javascripts take 374.2 kB which makes up the majority of the site volume.
Potential reduce by 27.5 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 27.5 kB or 74% of the original size.
Potential reduce by 8.6 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. Obviously, Orleo needs image optimization as it can save up to 8.6 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 291.2 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 291.2 kB or 78% of the original size.
Potential reduce by 37.7 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. Orleo.ru needs all CSS files to be minified and compressed as it can save up to 37.7 kB or 84% of the original size.
Number of requests can be reduced by 44 (80%)
55
11
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orleo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
orleo.ru
582 ms
style.css
142 ms
css_browser_selector.js
266 ms
navigation.css
267 ms
jquery.js
550 ms
header-487d058b-d559-f7ff-a42e-6cd2723cfac2.css
303 ms
text-bfdc149d-e852-bb2b-55b6-a1d514b6704d.css
303 ms
text.css
303 ms
text.js
401 ms
jquery.fitvids.js
400 ms
text-07ae70db-0fc5-b9ee-2cc5-f33c5aa154ea.css
444 ms
navigation-486f4142-de43-e4a0-b469-6d822e50f03f.css
442 ms
css
32 ms
text-a1618851-d756-6910-2feb-a1c50263b559.css
436 ms
text-990ca4bc-b5c4-750d-c08c-8a13b6234d73.css
536 ms
text-acf25ee0-76d9-6a89-5a29-1cebf3a5ae1c.css
536 ms
text-7b372108-ef26-59b0-73ce-50c407b23626.css
574 ms
layout.css
583 ms
helpers.js
587 ms
view.js
675 ms
929 ms
anti_cache.js
669 ms
css
18 ms
charity-philanthropic-organization_02.jpg
911 ms
external-border-none-top-left.png
153 ms
external-border-none-top-right.png
149 ms
external-border-none-top.png
148 ms
external-border-none-top-left2.png
148 ms
external-border-none-top-right2.png
146 ms
external-border-none-left.png
296 ms
external-border-none-left-top.png
296 ms
external-border-none-left-bottom.png
294 ms
external-border-none-right.png
295 ms
external-border-none-right-top.png
293 ms
external-border-none-right-bottom.png
425 ms
external-border-none-bottom-left.png
425 ms
external-border-none-bottom-right.png
425 ms
external-border-none-bottom.png
428 ms
external-border-none-bottom-left2.png
427 ms
external-border-none-bottom-right2.png
581 ms
border-none-top-left.png
580 ms
border-none-top-right.png
580 ms
border-none-top.png
580 ms
border-none-left.png
579 ms
border-none-right.png
718 ms
menu-toggle.png
715 ms
uYKcPVoh6c5R0NpdEY5A-Q.woff
24 ms
xpbXuAKcTwQ5l3JD46hcvQ.woff
32 ms
97 ms
193 ms
280 ms
286 ms
287 ms
border-none-bottom-left.png
445 ms
border-none-bottom-right.png
443 ms
border-none-bottom.png
440 ms
published_non-profit-organization_03.jpg
878 ms
watch.js
5 ms
UTF-8
705 ms
orleo.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.
orleo.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
orleo.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Orleo.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 Orleo.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.
orleo.ru
Open Graph description is not detected on the main page of Orleo. 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: