Aiz.Ru - Info aiz.ru

aiz.ru receives about 907 unique visitors and 1,814 (2.00 per visitor) page views per day which should earn about $0.92/day from advertising revenue. Estimated site value is $674.92. According to Alexa Traffic Rank aiz.ru is ranked number 1,868,043 in the world and 2.0E-5% of global Internet users visit it. Site is hosted in Russia and links to network IP address 176.99.3.45. This server doesn't support HTTPS and doesn't support HTTP/2.

About - aiz.ru


Technologies used on Website

Analytics
Liveinternet
Web Servers
Nginx
Reverse proxies
Nginx

aiz.ru Profile

Title: Южноуральский Арматурно-Изоляторный Завод
Last update was 134 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with aiz.ru in any way. Only publicly available statistics data are displayed.

How popular is aiz.ru?

0.9K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
907
Monthly Unique Visitors:
21,768
Pages per Visit:
2.00
Daily Pageviews:
1,814
Alexa Rank:
1,868,043 visit alexa
Alexa Reach:
2.0E-5%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Users%Pageviews%Rank
Russian Federation 51.5%25.1%199421

Where do visitors go on this site?

Reach%Pageviews%PerUser
aiz.ru
51.47%20.00%1
OTHER
0%80.00%0

Competitive Data

SEMrush
Domain:
  aiz.ru
Rank:
(Rank based on keywords, cost and organic traffic)
  15,459,229
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  33
Organic Traffic:
(Number of visitors coming from top 20 search results)
  2
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is aiz.ru?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
aiz.ru
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
aiz.ru
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much aiz.ru can earn?

Daily Revenue:
$0.92
Monthly Revenue:
$27.60
Yearly Revenue:
$335.80
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Russian Federation 455$0.92

How much money do aiz.ru lose due to Adblock?

Daily Revenue Loss:
$0.06
Monthly Revenue Loss:
$1.66
Yearly Revenue Loss:
$20.24
Daily Pageviews Blocked:
27
Monthly Pageviews Blocked:
820
Yearly Pageviews Blocked:
9,971
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Russian Federation 27$0.06

How much is aiz.ru worth?

Website Value:
$674.92

+ Where is aiz.ru hosted?

Server IP:
176.99.3.45
ASN:
AS197695 
ISP:
Domain names registrar REG.RU, Ltd 
Server Location:

Russia, RU
 

Other sites hosted on 176.99.3.45

There are no other sites hosted on this IP

+ How fast does aiz.ru load?

Average Load Time:
(361 ms) 98 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 50 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Minimize third-party usage - Third-party code blocked the main thread for 40 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
94 KB40 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
226 ms
8 ms
237 ms
5 ms
380 ms
14 ms
394 ms
24 ms
425 ms
12 ms
688 ms
105 ms
1093 ms
70 ms
1165 ms
53 ms
1256 ms
8 ms
1290 ms
12 ms
JavaScript execution time - 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
https://mc.yandex.ru/metrika/tag.js
222 ms211 ms9 ms
Other
220 ms75 ms1 ms
Properly size images - Potential savings of 504 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://aiz.ru/i/birthday/logo.png
512 KB499 KB
http://aiz.ru/files/images/421_kuzn-pres.jpg
28 KB4 KB
Avoids enormous network payloads - Total size was 839 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://aiz.ru/i/birthday/logo.png
512 KB
http://aiz.ru/files/images/zavod-juaiz.jpg
112 KB
https://mc.yandex.ru/metrika/tag.js
92 KB
http://aiz.ru/files/images/421_kuzn-pres.jpg
28 KB
http://aiz.ru/files/images/422_lite.jpg
18 KB
http://aiz.ru/i/fo10.jpg
17 KB
http://aiz.ru/files/images/423_laboratory.jpg
14 KB
http://aiz.ru/i/fo12.jpg
12 KB
http://aiz.ru/files/images/sert.jpg
9 KB
http://aiz.ru/
7 KB
Minimizes main-thread work - 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
291 ms
Other
66 ms
Rendering
47 ms
Style & Layout
27 ms
Script Parsing & Compilation
11 ms
Parse HTML & CSS
6 ms
Serve images in next-gen formats - Potential savings of 453 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://aiz.ru/i/birthday/logo.png
512 KB387 KB
http://aiz.ru/files/images/zavod-juaiz.jpg
112 KB65 KB
Avoids an excessive DOM size - 191 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
191
Maximum DOM Depth
9
Maximum Child Elements
34
Keep request counts low and transfer sizes small - 30 requests • 839 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
30839 KB
Image
23735 KB
Script
192 KB
Document
17 KB
Other
43 KB
Stylesheet
12 KB
Media
00 KB
Font
00 KB
Third-party
998 KB
Eliminate render-blocking resources - Potential savings of 40 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://aiz.ru/styl.css?2017080300
2 KB70
Efficiently encode images - Potential savings of 31 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://aiz.ru/files/images/zavod-juaiz.jpg
112 KB31 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://aiz.ru/
0 ms201 ms7 KB22 KB200text/htmlDocument
http://aiz.ru/styl.css?2017080300
215 ms354 ms2 KB6 KB200text/cssStylesheet
http://aiz.ru/i/birthday/logo.png
215 ms1176 ms512 KB512 KB200image/pngImage
http://aiz.ru/i/eng3.gif
215 ms355 ms1 KB1 KB200image/gifImage
http://aiz.ru/i/rus3.gif
216 ms393 ms1 KB0 KB200image/gifImage
http://aiz.ru/files/images/sert.jpg
217 ms354 ms9 KB8 KB200image/jpegImage
http://aiz.ru/files/images/zavod-juaiz.jpg
217 ms761 ms112 KB112 KB200image/jpegImage
http://aiz.ru/files/images/381_539-3990_IMG.jpg
217 ms357 ms1 KB1 KB404text/htmlImage
http://aiz.ru/files/images/422_lite.jpg
217 ms489 ms18 KB17 KB200image/jpegImage
http://aiz.ru/files/images/421_kuzn-pres.jpg
217 ms492 ms28 KB28 KB200image/jpegImage
http://aiz.ru/files/images/423_laboratory.jpg
217 ms488 ms14 KB14 KB200image/jpegImage
https://informer.yandex.ru/informer/25399274/3_1_FFFFFFFF_EFEFEFFF_0_pageviews
218 ms362 ms2 KB1 KB200image/pngImage
http://counter.yadro.ru/hit?t14.13;r;s800*600*24;uhttp%3A//aiz.ru/;0.015565989343199194
358 ms630 ms0 KB0 KB302text/html
https://mc.yandex.ru/metrika/tag.js
360 ms650 ms92 KB357 KB200application/javascriptScript
http://u6594.02.spylog.com/cnt?cid=659402&p=0&rn=0.15866279211889478&c=1&t=480&j=N&wh=800x600&px=24&sl=1.3&r=&fr=0&pg=http%3A//aiz.ru/
365 ms864 ms0 KB0 KB301text/html
http://aiz.ru/i/f1.gif
366 ms506 ms1 KB0 KB200image/gifImage
http://aiz.ru/i/f11.gif
366 ms507 ms0 KB0 KB200image/gifImage
http://aiz.ru/i/f10.gif
367 ms503 ms1 KB1 KB200image/gifImage
http://aiz.ru/i/fo10.jpg
367 ms638 ms17 KB16 KB200image/jpegImage
http://aiz.ru/i/fo11.gif
367 ms505 ms3 KB3 KB200image/gifImage
http://aiz.ru/i/fo12.jpg
368 ms505 ms12 KB12 KB200image/jpegImage
http://aiz.ru/i/but.gif
368 ms507 ms1 KB0 KB200image/gifImage
http://aiz.ru/i/f3.gif
369 ms507 ms0 KB0 KB200image/gifImage
http://aiz.ru/i/copy_bg.gif
369 ms506 ms0 KB0 KB200image/gifImage
http://aiz.ru/i/copy.gif
369 ms507 ms0 KB0 KB200image/gifImage
http://counter.yadro.ru/p.gif
630 ms769 ms0 KB0 KB200image/gifImage
https://mc.yandex.ru/watch/25399274?wmode=7&page-url=http%3A%2F%2Faiz.ru%2F&charset=utf-8&browser-info=ti%3A10%3Ans%3A1574615084112%3As%3A800x600x24%3Ask%3A1%3Ahdl%3A1%3Afpr%3A216613626101%3Acn%3A1%3Aw%3A1350x940%3Az%3A-480%3Ai%3A20191124090444%3Aet%3A1574615085%3Aen%3Autf-8%3Ac%3A1%3Ala%3Aen-us%3Antf%3A1%3Apv%3A1%3Als%3A646902028854%3Arqn%3A1%3Arn%3A905707649%3Ahid%3A879739389%3Ads%3A0%2C0%2C202%2C0%2C0%2C0%2C0%2C157%2C0%2C%2C%2C%2C366%3Afp%3A434%3Awn%3A17757%3Ahl%3A2%3Agdpr%3A14%3Av%3A1747%3Awv%3A2%3Arqnl%3A1%3Ast%3A1574615085%3Au%3A1574615085118335355%3At%3A%D0%AE%D0%B6%D0%BD%D0%BE%D1%83%D1%80%D0%B0%D0%BB%D1%8C%D1%81%D0%BA%D0%B8%D0%B9%20%D0%90%D1%80%D0%BC%D0%B0%D1%82%D1%83%D1%80%D0%BD%D0%BE-%D0%98%D0%B7%D0%BE%D0%BB%D1%8F%D1%82%D0%BE%D1%80%D0%BD%D1%8B%D0%B9%20%D0%97%D0%B0%D0%B2%D0%BE%D0%B4
768 ms920 ms2 KB0 KB302
https://mc.yandex.ru/metrika/advert.gif
778 ms926 ms0 KB0 KB200image/gifImage
https://openstat.net/digits?cid=659402&p=0&rn=0.15866279211889478&c=1&t=480&j=N&wh=800x600&px=24&sl=1.3&r=&fr=0&pg=http%3A//aiz.ru/
864 ms983 ms1 KB1 KB200image/pngImage
https://mc.yandex.ru/watch/25399274/1?wmode=7&page-url=http%3A%2F%2Faiz.ru%2F&charset=utf-8&browser-info=ti%3A10%3Ans%3A1574615084112%3As%3A800x600x24%3Ask%3A1%3Ahdl%3A1%3Afpr%3A216613626101%3Acn%3A1%3Aw%3A1350x940%3Az%3A-480%3Ai%3A20191124090444%3Aet%3A1574615085%3Aen%3Autf-8%3Ac%3A1%3Ala%3Aen-us%3Antf%3A1%3Apv%3A1%3Als%3A646902028854%3Arqn%3A1%3Arn%3A905707649%3Ahid%3A879739389%3Ads%3A0%2C0%2C202%2C0%2C0%2C0%2C0%2C157%2C0%2C%2C%2C%2C366%3Afp%3A434%3Awn%3A17757%3Ahl%3A2%3Agdpr%3A14%3Av%3A1747%3Awv%3A2%3Arqnl%3A1%3Ast%3A1574615085%3Au%3A1574615085118335355%3At%3A%D0%AE%D0%B6%D0%BD%D0%BE%D1%83%D1%80%D0%B0%D0%BB%D1%8C%D1%81%D0%BA%D0%B8%D0%B9%20%D0%90%D1%80%D0%BC%D0%B0%D1%82%D1%83%D1%80%D0%BD%D0%BE-%D0%98%D0%B7%D0%BE%D0%BB%D1%8F%D1%82%D0%BE%D1%80%D0%BD%D1%8B%D0%B9%20%D0%97%D0%B0%D0%B2%D0%BE%D0%B4
920 ms1070 ms1 KB0 KB200application/jsonXHR
Serve static assets with an efficient cache policy - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://mc.yandex.ru/metrika/tag.js
3600000 ms92 KB
https://mc.yandex.ru/metrika/advert.gif
3600000 ms0 KB
Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid chaining critical requests - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 200 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

98
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Total Blocking Time 150 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Contentful Paint (3G) 1560 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 190 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 2.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
349 ms
9 ms
361 ms
6 ms
505 ms
13 ms
518 ms
24 ms
545 ms
13 ms
961 ms
96 ms
1716 ms
67 ms
1786 ms
55 ms
1912 ms
14 ms
JavaScript execution time - 1.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
874 ms295 ms5 ms
https://mc.yandex.ru/metrika/tag.js
847 ms811 ms30 ms
Properly size images - Potential savings of 425 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://aiz.ru/i/birthday/logo.png
512 KB425 KB
Avoids enormous network payloads - Total size was 839 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://aiz.ru/i/birthday/logo.png
512 KB
http://aiz.ru/files/images/zavod-juaiz.jpg
112 KB
https://mc.yandex.ru/metrika/tag.js
92 KB
http://aiz.ru/files/images/421_kuzn-pres.jpg
28 KB
http://aiz.ru/files/images/422_lite.jpg
18 KB
http://aiz.ru/i/fo10.jpg
17 KB
http://aiz.ru/files/images/423_laboratory.jpg
14 KB
http://aiz.ru/i/fo12.jpg
12 KB
http://aiz.ru/files/images/sert.jpg
9 KB
http://aiz.ru/
7 KB
Minimizes main-thread work - 1.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
1121 ms
Other
268 ms
Rendering
168 ms
Style & Layout
119 ms
Script Parsing & Compilation
40 ms
Parse HTML & CSS
25 ms
Garbage Collection
2 ms
Serve images in next-gen formats - Potential savings of 453 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://aiz.ru/i/birthday/logo.png
512 KB387 KB
http://aiz.ru/files/images/zavod-juaiz.jpg
112 KB65 KB
Avoids an excessive DOM size - 191 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
191
Maximum DOM Depth
9
Maximum Child Elements
34
Keep request counts low and transfer sizes small - 30 requests • 839 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
30839 KB
Image
23735 KB
Script
192 KB
Document
17 KB
Other
43 KB
Stylesheet
12 KB
Media
00 KB
Font
00 KB
Third-party
998 KB
Eliminate render-blocking resources - Potential savings of 80 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://aiz.ru/styl.css?2017080300
2 KB180
Efficiently encode images - Potential savings of 31 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://aiz.ru/files/images/zavod-juaiz.jpg
112 KB31 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://aiz.ru/
0 ms307 ms7 KB22 KB200text/htmlDocument
http://aiz.ru/styl.css?2017080300
323 ms465 ms2 KB6 KB200text/cssStylesheet
http://aiz.ru/i/birthday/logo.png
324 ms1142 ms512 KB512 KB200image/pngImage
http://aiz.ru/i/eng3.gif
324 ms465 ms1 KB1 KB200image/gifImage
http://aiz.ru/i/rus3.gif
325 ms467 ms1 KB0 KB200image/gifImage
http://aiz.ru/files/images/sert.jpg
326 ms466 ms9 KB8 KB200image/jpegImage
http://aiz.ru/files/images/zavod-juaiz.jpg
326 ms869 ms112 KB112 KB200image/jpegImage
http://aiz.ru/files/images/381_539-3990_IMG.jpg
326 ms505 ms1 KB1 KB404text/htmlImage
http://aiz.ru/files/images/422_lite.jpg
326 ms600 ms18 KB17 KB200image/jpegImage
http://aiz.ru/files/images/421_kuzn-pres.jpg
326 ms600 ms28 KB28 KB200image/jpegImage
http://aiz.ru/files/images/423_laboratory.jpg
327 ms597 ms14 KB14 KB200image/jpegImage
https://informer.yandex.ru/informer/25399274/3_1_FFFFFFFF_EFEFEFFF_0_pageviews
327 ms887 ms2 KB1 KB200image/pngImage
https://mc.yandex.ru/metrika/tag.js
468 ms906 ms92 KB357 KB200application/javascriptScript
http://counter.yadro.ru/hit?t14.13;r;s412*660*24;uhttp%3A//aiz.ru/;0.9984513673354101
469 ms741 ms0 KB0 KB302text/html
http://u6594.02.spylog.com/cnt?cid=659402&p=0&rn=0.9737803151613273&c=1&t=480&j=N&wh=412x660&px=24&sl=1.3&r=&fr=0&pg=http%3A//aiz.ru/
473 ms834 ms0 KB0 KB301text/html
http://aiz.ru/i/f1.gif
474 ms614 ms1 KB0 KB200image/gifImage
http://aiz.ru/i/f11.gif
474 ms616 ms0 KB0 KB200image/gifImage
http://aiz.ru/i/f10.gif
475 ms749 ms1 KB1 KB200image/gifImage
http://aiz.ru/i/fo10.jpg
475 ms748 ms17 KB16 KB200image/jpegImage
http://aiz.ru/i/fo11.gif
476 ms748 ms3 KB3 KB200image/gifImage
http://aiz.ru/i/fo12.jpg
476 ms749 ms12 KB12 KB200image/jpegImage
http://aiz.ru/i/but.gif
477 ms616 ms1 KB0 KB200image/gifImage
http://aiz.ru/i/f3.gif
477 ms617 ms0 KB0 KB200image/gifImage
http://aiz.ru/i/copy_bg.gif
478 ms618 ms0 KB0 KB200image/gifImage
http://aiz.ru/i/copy.gif
478 ms618 ms0 KB0 KB200image/gifImage
http://counter.yadro.ru/p.gif
742 ms879 ms0 KB0 KB200image/gifImage
https://openstat.net/digits?cid=659402&p=0&rn=0.9737803151613273&c=1&t=480&j=N&wh=412x660&px=24&sl=1.3&r=&fr=0&pg=http%3A//aiz.ru/
834 ms945 ms1 KB1 KB200image/pngImage
https://mc.yandex.ru/watch/25399274?wmode=7&page-url=http%3A%2F%2Faiz.ru%2F&charset=utf-8&browser-info=ti%3A10%3Ans%3A1574615076107%3As%3A412x660x24%3Ask%3A2.625%3Ahdl%3A1%3Afpr%3A216613626101%3Acn%3A1%3Aw%3A980x1569%3Az%3A-480%3Ai%3A20191124090437%3Aet%3A1574615077%3Aen%3Autf-8%3Ac%3A1%3Ala%3Aen-us%3Antf%3A1%3Apv%3A1%3Als%3A661906757374%3Arqn%3A1%3Arn%3A466220126%3Ahid%3A492384314%3Ads%3A0%2C0%2C308%2C0%2C1%2C0%2C0%2C157%2C1%2C%2C%2C%2C474%3Afp%3A529%3Awn%3A35835%3Ahl%3A2%3Agdpr%3A14%3Av%3A1747%3Awv%3A2%3Arqnl%3A1%3Ast%3A1574615077%3Au%3A157461507793873875%3At%3A%D0%AE%D0%B6%D0%BD%D0%BE%D1%83%D1%80%D0%B0%D0%BB%D1%8C%D1%81%D0%BA%D0%B8%D0%B9%20%D0%90%D1%80%D0%BC%D0%B0%D1%82%D1%83%D1%80%D0%BD%D0%BE-%D0%98%D0%B7%D0%BE%D0%BB%D1%8F%D1%82%D0%BE%D1%80%D0%BD%D1%8B%D0%B9%20%D0%97%D0%B0%D0%B2%D0%BE%D0%B4
1016 ms1523 ms2 KB0 KB302
https://mc.yandex.ru/metrika/advert.gif
1026 ms1177 ms0 KB0 KB200image/gifImage
https://mc.yandex.ru/watch/25399274/1?wmode=7&page-url=http%3A%2F%2Faiz.ru%2F&charset=utf-8&browser-info=ti%3A10%3Ans%3A1574615076107%3As%3A412x660x24%3Ask%3A2.625%3Ahdl%3A1%3Afpr%3A216613626101%3Acn%3A1%3Aw%3A980x1569%3Az%3A-480%3Ai%3A20191124090437%3Aet%3A1574615077%3Aen%3Autf-8%3Ac%3A1%3Ala%3Aen-us%3Antf%3A1%3Apv%3A1%3Als%3A661906757374%3Arqn%3A1%3Arn%3A466220126%3Ahid%3A492384314%3Ads%3A0%2C0%2C308%2C0%2C1%2C0%2C0%2C157%2C1%2C%2C%2C%2C474%3Afp%3A529%3Awn%3A35835%3Ahl%3A2%3Agdpr%3A14%3Av%3A1747%3Awv%3A2%3Arqnl%3A1%3Ast%3A1574615077%3Au%3A157461507793873875%3At%3A%D0%AE%D0%B6%D0%BD%D0%BE%D1%83%D1%80%D0%B0%D0%BB%D1%8C%D1%81%D0%BA%D0%B8%D0%B9%20%D0%90%D1%80%D0%BC%D0%B0%D1%82%D1%83%D1%80%D0%BD%D0%BE-%D0%98%D0%B7%D0%BE%D0%BB%D1%8F%D1%82%D0%BE%D1%80%D0%BD%D1%8B%D0%B9%20%D0%97%D0%B0%D0%B2%D0%BE%D0%B4
1523 ms1677 ms1 KB0 KB200application/jsonXHR
Serve static assets with an efficient cache policy - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://mc.yandex.ru/metrika/tag.js
3600000 ms92 KB
https://mc.yandex.ru/metrika/advert.gif
3600000 ms0 KB
Reduce the impact of third-party code - Third-party code blocked the main thread for 450 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
94 KB447 ms
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid chaining critical requests - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 310 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Currently Not Available

+ Does aiz.ru use compression?

aiz.ru use gzip compression.
Original size: 21.93 KB
Compressed size: 7 KB
File reduced by: 14.93 KB (68%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

aiz.ru does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

aiz.ru does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Sun, 24 Nov 2019 17:04:17 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: ClientID=157461505735705193861304; path=/; domain=.aiz.ru; expires=Mon, 23-Nov-2020 17:04:17 GMT
X-Powered-By: Flexites
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
TXT 3600
TXT 3600
TXT 3600
TXT 3600
MX mx2.aiz.ru 3600
MX mx.aiz.ru 3600
SOA 3600
Mname ns3-l2.nic.ru
Rname hostmaster.aiz.ru
Serial Number 2014071905
Refresh 10800
Retry 3600
Expire 604800
Minimum TTL 0
A 176.99.3.45 3600
NS ns8-l2.nic.ru 3568
NS ns8-cloud.nic.ru 3568
NS ns4-cloud.nic.ru 3568
NS ns3-l2.nic.ru 3568
NS ns4-l2.nic.ru 3568

+ Whois Lookup

Domain Created:
2000-03-03
Domain Age:
19 years 8 months 21 days  
WhoIs:
 

whois lookup at whois.tcinet.ru...
% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: AIZ.RU
nserver: ns3-l2.nic.ru.
nserver: ns4-cloud.nic.ru.
nserver: ns4-l2.nic.ru.
nserver: ns8-cloud.nic.ru.
nserver: ns8-l2.nic.ru.
state: REGISTERED, DELEGATED, VERIFIED
org: YuAIZ AO
registrar: RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created: 2000-03-03T16:06:50Z
paid-till: 2020-03-31T21:00:00Z
free-date: 2020-05-02
source: TCI

Last updated on 2019-11-24T17:01:30Z
Last update was 134 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with aiz.ru in any way. Only publicly available statistics data are displayed.
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
aiz.ru widget