6.8 sec in total
1.6 sec
4.8 sec
419 ms
Welcome to inari.ru homepage info - get ready to check INARI best content for Russia right away, or after learning these important things about inari.ru
Изготовление корпоративной и представительской продукции. Широкий спектр текстильных бизнес-сувениров и печати на ткани. Розничная и крупнооптовая продажа.
Visit inari.ruWe analyzed Inari.ru page load time and found that the first response time was 1.6 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
inari.ru performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value15.5 s
0/100
25%
Value11.5 s
5/100
10%
Value5,590 ms
0/100
30%
Value0.974
2/100
15%
Value14.4 s
9/100
10%
1555 ms
123 ms
163 ms
116 ms
178 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 91% of them (71 requests) were addressed to the original Inari.ru, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Inari.ru.
Page size can be reduced by 576.9 kB (39%)
1.5 MB
906.9 kB
In fact, the total size of Inari.ru main page is 1.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. 55% of websites need less resources to load. Images take 863.7 kB which makes up the majority of the site volume.
Potential reduce by 67.2 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 67.2 kB or 78% of the original size.
Potential reduce by 109.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, INARI needs image optimization as it can save up to 109.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 264.4 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 264.4 kB or 71% of the original size.
Potential reduce by 135.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. Inari.ru needs all CSS files to be minified and compressed as it can save up to 135.7 kB or 84% of the original size.
Number of requests can be reduced by 33 (44%)
75
42
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INARI. 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 from 13 to 1 for CSS and as a result speed up the page load time.
inari.ru
1555 ms
jquery.min.js
123 ms
jquery-migrate-1.2.1.js
163 ms
jquery.corner.js
116 ms
highslide.css
178 ms
highslide-sitestyles.css
184 ms
prettyPhoto.css
190 ms
modal.css
186 ms
form.css
188 ms
chosen.css
194 ms
finder.css
259 ms
style.css
264 ms
vmsite-ltr.css
270 ms
mootools-core.js
361 ms
core.js
274 ms
caption.js
271 ms
highslide-full.packed.js
339 ms
easing_equations.js
341 ms
swfobject.js
349 ms
en.js
354 ms
highslide-sitesettings.js
351 ms
copylink.js
420 ms
jquery.prettyPhoto.js
427 ms
modal.js
442 ms
chosen.jquery.min.js
438 ms
autocompleter.js
445 ms
script.js
447 ms
template_main.css
506 ms
home.css
510 ms
style.css
521 ms
nivo-slider.css
521 ms
jquery.nivo.slider.js
529 ms
slide-show.js
527 ms
button-up.js
529 ms
js.js
530 ms
jquery.corner.js
54 ms
header.jpg
561 ms
logo.png
622 ms
logo-4d.png
592 ms
button.gif
591 ms
glavnaya-akciya-1.png
653 ms
glavnaya-akciya-2.png
1495 ms
glavnaya-akciya-3.png
678 ms
glavnaya-akciya-4.png
1611 ms
ten-reasons-01.jpg
1526 ms
ten-reasons-03.jpg
1071 ms
ten-reasons-04.jpg
891 ms
ten-reasons-02.jpg
1504 ms
ten-reasons-05.jpg
1104 ms
ten-reasons-10.jpg
1594 ms
ten-reasons-09.jpg
1198 ms
ten-reasons-07.jpg
1365 ms
ten-reasons-06.jpg
1593 ms
ten-reasons-08.jpg
1840 ms
korp-klientam-1.png
1667 ms
korp-klientam-2.png
1688 ms
korp-klientam-3.png
1801 ms
n.jpg
1668 ms
n.jpg
1802 ms
n.jpg
1834 ms
preim-01.png
1752 ms
preim-02.png
1826 ms
preim-03.png
1845 ms
preim-04.png
2125 ms
preim-05.png
1994 ms
preim-06.png
2139 ms
preim-07.png
2140 ms
preim-08.png
2092 ms
vertical-separator.png
2101 ms
icons2.png
2605 ms
watch.js
511 ms
analytics.js
511 ms
span-left.png
1783 ms
span-right.png
1705 ms
collect
165 ms
glossy-dark.png
114 ms
zmout.cur
114 ms
loader.white.gif
113 ms
inari.ru accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
inari.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
Missing source maps for large first-party JavaScript
inari.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
EN
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inari.ru can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Russian language. Our system also found out that Inari.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.
inari.ru
Open Graph description is not detected on the main page of INARI. 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: