3.2 sec in total
497 ms
2.3 sec
360 ms
Welcome to orekh.com homepage info - get ready to check Orekh best content for Russia right away, or after learning these important things about orekh.com
Компания "Орехпром" является крупнейшим поставщиком орехов и осуществляет продажу орехов оптом и в розницу.
Visit orekh.comWe analyzed Orekh.com page load time and found that the first response time was 497 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
orekh.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value6.4 s
10/100
25%
Value10.4 s
8/100
10%
Value4,230 ms
1/100
30%
Value0.023
100/100
15%
Value14.1 s
9/100
10%
497 ms
134 ms
386 ms
258 ms
242 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 19% of them (9 requests) were addressed to the original Orekh.com, 17% (8 requests) were made to Apis.google.com and 9% (4 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Orekh.com.
Page size can be reduced by 690.5 kB (43%)
1.6 MB
933.7 kB
In fact, the total size of Orekh.com main page is 1.6 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 825.0 kB which makes up the majority of the site volume.
Potential reduce by 132.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. 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 132.6 kB or 75% of the original size.
Potential reduce by 996 B
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. Orekh images are well optimized though.
Potential reduce by 545.1 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 545.1 kB or 66% of the original size.
Potential reduce by 11.9 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. Orekh.com needs all CSS files to be minified and compressed as it can save up to 11.9 kB or 78% of the original size.
Number of requests can be reduced by 28 (62%)
45
17
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orekh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
orekh.com
497 ms
style.css
134 ms
jquery-1.3.min.js
386 ms
js.js
258 ms
share.js
242 ms
addthis_widget.js
11 ms
logo
288 ms
bgSkorlupa.jpg
1022 ms
bgSkorlupaHead.jpg
640 ms
logo.png
174 ms
bgLight.png
287 ms
bgDark.png
287 ms
share.php
165 ms
share_logo.png
272 ms
ga.js
20 ms
300lo.json
71 ms
widgets.js
7 ms
all.js&version=v2.0
442 ms
plusone.js
74 ms
counter.5524cceca805eb4b9b2b.js
45 ms
sh.8e5f85691f9aaa082472a194.html
60 ms
__utm.gif
45 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
47 ms
shares.json
74 ms
layers.e5ea973510bf60b3db41.js
16 ms
cb=gapi.loaded_0
115 ms
cb=gapi.loaded_1
114 ms
fastbutton
177 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
22 ms
watch.js
462 ms
postmessageRelay
63 ms
cb=gapi.loaded_0
33 ms
cb=gapi.loaded_1
31 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
56 ms
3193398744-postmessagerelay.js
31 ms
rpc:shindig_random.js
36 ms
cb=gapi.loaded_0
3 ms
jot
113 ms
40 ms
xd_arbiter.php
134 ms
xd_arbiter.php
266 ms
advert.gif
96 ms
1
85 ms
ping
12 ms
like.php
57 ms
qeKvIRsJabD.js
288 ms
LVx-xkvaJ0b.png
325 ms
orekh.com 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.
orekh.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
orekh.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
RU
EN
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Orekh.com can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Orekh.com 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.
orekh.com
Open Graph description is not detected on the main page of Orekh. 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: