Nawasco.Com.Vn - Info receives about 85 unique visitors and 509 (6.00 per visitor) page views per day which should earn about $2.08/day from advertising revenue. Estimated site value is $881.97. According to Alexa Traffic Rank is ranked number 3,462,862 in the world and 5.0E-6% of global Internet users visit it. Site is hosted in Vietnam and links to network IP address This server doesn't support HTTPS and doesn't support HTTP/2.

About -

Technologies used on Website

UI frameworks
Web Servers
Web Frameworks
Microsoft ASP.NET Profile

Title: Công ty cổ phần cấp nước Nghệ An
Last update was 159 days ago
This can take up to 60 seconds. Please wait...

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

How popular is

85 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
3,462,862 visit alexa
Alexa Reach:
5.0E-6%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

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

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

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

Desktop summary

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

Mobile summary

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

+ Abusive Experience Report

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

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Viettel Group 
Server Location:

Vietnam, VN

Other sites hosted on

There are no other sites hosted on this IP

+ How fast does load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

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 1.0 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.6 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.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 30 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.
Third-Party Usage
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.

Screenshot Thumbnails

This is what the load of your site looked like.

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

Start Time
End Time
361 ms
8 ms
371 ms
6 ms
663 ms
6 ms
673 ms
42 ms
720 ms
21 ms
1000 ms
25 ms
1027 ms
7 ms
1223 ms
33 ms
1889 ms
8 ms
Minify CSS - Potential savings of 26 KB
Minifying CSS files can reduce network payload sizes. Learn more.

SizePotential Savings
143 KB24 KB
10 KB2 KB
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
167 ms3 ms1 ms
Properly size images - Potential savings of 608 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
330 KB290 KB
225 KB218 KB
102 KB99 KB
Remove unused CSS - Potential savings of 145 KB
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.

SizePotential Savings
143 KB134 KB
10 KB7 KB
4 KB4 KB
Avoids enormous network payloads - Total size was 2,630 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

432 KB
371 KB
330 KB
262 KB
225 KB
143 KB
130 KB
103 KB
68 KB
65 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Time Spent
Script Evaluation
57 ms
56 ms
50 ms
Style & Layout
42 ms
Script Parsing & Compilation
15 ms
Parse HTML & CSS
14 ms
Serve images in next-gen formats - Potential savings of 1,144 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.

SizePotential Savings
370 KB242 KB
330 KB193 KB
225 KB191 KB
129 KB71 KB
49 KB43 KB
47 KB42 KB
44 KB40 KB
44 KB40 KB
41 KB37 KB
38 KB33 KB
65 KB33 KB
102 KB31 KB
35 KB31 KB
36 KB30 KB
36 KB30 KB
56 KB29 KB
33 KB28 KB
Avoids an excessive DOM size - 251 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Minify JavaScript - Potential savings of 335 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

SizePotential Savings
432 KB183 KB
262 KB128 KB
68 KB23 KB
Keep request counts low and transfer sizes small - 27 requests • 2,630 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
272630 KB
171685 KB
4764 KB
5162 KB
119 KB
00 KB
00 KB
00 KB
00 KB
Eliminate render-blocking resources - Potential savings of 450 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.

SizePotential Savings
4 KB70
1 KB110
143 KB310
10 KB150
4 KB110
Efficiently encode images - Potential savings of 101 KB
Optimized images load faster and consume less cellular data. Learn more.

SizePotential Savings
370 KB46 KB
330 KB40 KB
65 KB8 KB
56 KB7 KB
Enable text compression - Potential savings of 740 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

SizePotential Savings
432 KB352 KB
262 KB184 KB
143 KB122 KB
68 KB54 KB
19 KB14 KB
10 KB8 KB
4 KB3 KB
3 KB3 KB
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms335 ms19 KB19 KB200text/htmlDocument
349 ms606 ms4 KB4 KB200text/cssStylesheet
349 ms605 ms1 KB1 KB200text/cssStylesheet
350 ms639 ms143 KB143 KB200text/cssStylesheet
350 ms609 ms10 KB10 KB200text/cssStylesheet
350 ms599 ms4 KB3 KB200text/cssStylesheet
350 ms640 ms225 KB225 KB200image/pngImage
350 ms1846 ms330 KB330 KB200image/jpegImage
647 ms990 ms371 KB370 KB200image/jpegImage
647 ms1159 ms65 KB65 KB200image/jpegImage
647 ms1169 ms56 KB56 KB200image/jpegImage
648 ms1231 ms103 KB102 KB200image/jpegImage
648 ms1249 ms33 KB33 KB200image/pngImage
648 ms1418 ms49 KB49 KB200image/pngImage
648 ms1417 ms36 KB36 KB200image/pngImage
648 ms1447 ms35 KB35 KB200image/pngImage
648 ms1495 ms44 KB44 KB200image/pngImage
648 ms1501 ms47 KB47 KB200image/pngImage
649 ms1668 ms44 KB44 KB200image/pngImage
649 ms1678 ms41 KB41 KB200image/pngImage
649 ms1707 ms36 KB36 KB200image/pngImage
649 ms1767 ms39 KB38 KB200image/pngImage
647 ms967 ms262 KB262 KB200application/javascriptScript
647 ms916 ms68 KB68 KB200application/javascriptScript
647 ms1189 ms432 KB432 KB200application/javascriptScript
647 ms899 ms1 KB1 KB200application/javascriptScript
654 ms1762 ms130 KB129 KB200image/pngImage
Serve static assets with an efficient cache policy - 26 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
0 ms432 KB
0 ms371 KB
0 ms330 KB
0 ms262 KB
0 ms225 KB
0 ms143 KB
0 ms130 KB
0 ms103 KB
0 ms68 KB
0 ms65 KB
0 ms56 KB
0 ms49 KB
0 ms47 KB
0 ms44 KB
0 ms44 KB
0 ms41 KB
0 ms39 KB
0 ms36 KB
0 ms36 KB
0 ms35 KB
0 ms33 KB
0 ms10 KB
0 ms4 KB
0 ms4 KB
0 ms1 KB
0 ms1 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.

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.

Minimize Critical Requests Depth - 9 chains 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.

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 340 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Page Speed (Google PageSpeed Insights) - Mobile

Currently Not Available

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 740.3KiB (78% reduction).

Compressing could save 351.7KiB (81% reduction).
Compressing could save 184.2KiB (70% reduction).
Compressing could save 121.8KiB (85% reduction).
Compressing could save 54KiB (79% reduction).
Compressing could save 14.4KiB (77% reduction).
Compressing could save 7.5KiB (77% reduction).
Compressing could save 3.3KiB (81% reduction).
Compressing could save 2.6KiB (74% reduction).
Compressing could save 646B (60% reduction).
Compressing could save 309B (50% reduction).

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 383.7KiB (42% reduction).

Compressing could save 159.1KiB (43% reduction).
Compressing could save 150.6KiB (46% reduction).
Compressing could save 27.2KiB (43% reduction).
Compressing could save 23.5KiB (23% reduction).
Compressing could save 23.2KiB (42% reduction).

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 321KiB (43% reduction).

Minifying could save 171.3KiB (40% reduction).
Minifying could save 127.3KiB (49% reduction).
Minifying could save 22.2KiB (33% reduction).
Minifying could save 277B (27% reduction).

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources: (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified)

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 21.2KiB (14% reduction).

Minifying could save 17KiB (12% reduction).
Minifying could save 2.5KiB (26% reduction).
Minifying could save 880B (25% reduction).
Minifying could save 772B (19% reduction).
Minifying could save 143B (23% reduction).

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 6.1KiB (33% reduction).

Minifying could save 6.1KiB (33% reduction).
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? does not use compression.
Original size: 18.65 KB
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify does not support HTTPS
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Cache-Control: no-cache, no-store
Pragma: no-cache
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8
Server: Kestrel
Set-Cookie: .AspNetCore.Antiforgery.9B36BhP9RIo=CfDJ8J3VXGn0yS1Ii_1HlhgwDGbHZn4Ls4ZYPSd0AadoyteGgDXQW9HojaoFMRLkMYEvZOFMW_PFYKLSvhK9gHitUYov9WP8MqQrswFAQoZ1g50ph9VRXK17toWysbSMlTQvpaU4X44STXopAZVCriQ-sAU; path=/; samesite=strict; httponly
Set-Cookie: XSRF-TOKEN=CfDJ8J3VXGn0yS1Ii_1HlhgwDGYcrHOyCJ2DIAthnr23mnrcX95rBwuRxMPQWiK_lCqquzXl3RO9-giUqS_UUUDf9mxPqU1G8upmvRn29lbK7oPoM2PDCJkyeMJXYnW9h7LBr56HH-G4pLwbhvO5kuavMww; path=/
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
Date: Sun, 22 Sep 2019 19:14:04 GMT

+ DNS Lookup

Type Ip Target TTL
TXT 360
MX 360
SOA 360
Serial Number 2019071009
Refresh 14400
Retry 3600
Expire 604800
Minimum TTL 0
A 360
NS 360
NS 360
NS 360

+ Whois Lookup

Domain Created:
Domain Age:

Currently Not Available
Last update was 159 days ago
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites
23 secs
36 secs
37 secs
1 min
1 min
2 mins
2 mins
2 mins
3 mins
3 mins
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


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) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget