Nuagedigite.Ch - Info receives about 2,359 unique visitors and 5,425 (2.30 per visitor) page views per day which should earn about $22.14/day from advertising revenue. Estimated site value is $16,158.87. According to Alexa Traffic Rank is ranked number 825,118 in the world and 5.2E-5% of global Internet users visit it. Site is hosted in Mountain View, California, 94043, United States and links to network IP address This server supports HTTPS and HTTP/2.

About -

Technologies used on Website

Font Scripts
Google Font API
Live Chat Profile

Title: Bad Request
Last update was 126 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

2.4K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
825,118 visit alexa
Alexa Reach:
5.2E-5%   (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:
Google LLC 
Server Location:
Mountain View
California, CA
United States, US

Other sites hosted on

+ How fast does load?

Average Load Time:
(1183 ms) 73 % 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

Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.0 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 1.0 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 1.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. 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.
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.

Screenshot Thumbnails

This is what the load of your site looked like.

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
201 ms9 ms1 ms
Properly size images - Potential savings of 9 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
19 KB9 KB
Avoids enormous network payloads - Total size was 1,102 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

268 KB
195 KB
90 KB
87 KB
39 KB
30 KB
20 KB
19 KB
19 KB
19 KB
Minimizes main-thread work - 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.

Time Spent
Script Evaluation
104 ms
103 ms
Style & Layout
53 ms
25 ms
Parse HTML & CSS
14 ms
Script Parsing & Compilation
8 ms
Serve images in next-gen formats - Potential savings of 245 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
268 KB122 KB
194 KB65 KB
90 KB41 KB
39 KB17 KB
Avoids an excessive DOM size - 222 elements
A large DOM will 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 12 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

SizePotential Savings
30 KB12 KB
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 49 requests • 1,102 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
491102 KB
20634 KB
19318 KB
4124 KB
420 KB
15 KB
10 KB
00 KB
22396 KB
Eliminate render-blocking resources - Potential savings of 200 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
3 KB70
9 KB150
6 KB150
6 KB230
Enable text compression - Potential savings of 56 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

SizePotential Savings
86 KB56 KB
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms138 ms0 KB0 KB301text/plain
139 ms215 ms5 KB18 KB200text/htmlDocument
227 ms302 ms3 KB8 KB200text/cssStylesheet
227 ms474 ms9 KB38 KB200text/cssStylesheet
228 ms305 ms6 KB48 KB200text/cssStylesheet
228 ms235 ms6 KB13 KB200text/javascriptScript
228 ms456 ms7 KB7 KB200image/pngImage
229 ms602 ms39 KB39 KB200image/pngImage
486 ms563 ms1 KB1 KB200image/svg+xmlImage
487 ms562 ms1 KB1 KB200image/svg+xmlImage
487 ms701 ms1 KB1 KB200image/svg+xmlImage
487 ms563 ms1 KB1 KB200image/svg+xmlImage
487 ms561 ms1 KB1 KB200image/svg+xmlImage
487 ms581 ms1 KB1 KB200image/svg+xmlImage
488 ms701 ms1 KB1 KB200image/svg+xmlImage
488 ms577 ms1 KB1 KB200image/svg+xmlImage
488 ms562 ms1 KB1 KB200image/svg+xmlImage
488 ms565 ms1 KB1 KB200image/svg+xmlImage
488 ms813 ms20 KB19 KB200image/pngImage
488 ms562 ms2 KB2 KB200image/pngImage
488 ms563 ms2 KB2 KB200image/pngImage
488 ms563 ms1 KB1 KB200image/svg+xmlImage
489 ms727 ms1 KB1 KB200image/svg+xmlImage
457 ms599 ms87 KB86 KB200application/javascriptScript
486 ms627 ms30 KB111 KB200application/javascriptScript,300italic,400,400italic,600,600italic,700,700italic,800,800italic%7CMerriweather:300,300italic,400,400italic,700,700italic,900,900italic
485 ms508 ms2 KB39 KB200text/cssStylesheet
492 ms1035 ms268 KB268 KB200image/jpegImage
493 ms835 ms195 KB194 KB200image/jpegImage
494 ms837 ms90 KB90 KB200image/jpegImage
495 ms633 ms19 KB35 KB200application/x-font-ttfFont
526 ms530 ms15 KB15 KB200font/woff2Font
527 ms532 ms14 KB14 KB200font/woff2Font
530 ms539 ms15 KB14 KB200font/woff2Font
532 ms536 ms14 KB13 KB200font/woff2Font
534 ms539 ms15 KB15 KB200font/woff2Font
535 ms541 ms14 KB14 KB200font/woff2Font
537 ms541 ms15 KB15 KB200font/woff2Font
538 ms543 ms14 KB14 KB200font/woff2Font
540 ms548 ms15 KB15 KB200font/woff2Font
542 ms549 ms14 KB14 KB200font/woff2Font
544 ms553 ms19 KB19 KB200font/woff2Font
545 ms553 ms19 KB19 KB200font/woff2Font
546 ms552 ms19 KB19 KB200font/woff2Font
548 ms553 ms19 KB19 KB200font/woff2Font
550 ms553 ms19 KB18 KB200font/woff2Font
551 ms556 ms19 KB19 KB200font/woff2Font
552 ms561 ms19 KB19 KB200font/woff2Font
554 ms561 ms19 KB19 KB200font/woff2Font
688 ms722 ms2 KB0 KB403text/htmlScript
Minimize third-party usage - Third-party code blocked the main thread for 0 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.

SizeMain-Thread Blocking Time
6 KB0 ms
2 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
239 ms
7 ms
499 ms
12 ms
512 ms
23 ms
539 ms
39 ms
578 ms
11 ms
641 ms
15 ms
670 ms
17 ms
687 ms
11 ms
698 ms
13 ms
712 ms
10 ms
721 ms
13 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
4 ms
5 ms
9 ms
4 ms
5 ms
6 ms
4 ms
4 ms
8 ms
7 ms
9 ms
8 ms
6 ms
5 ms
4 ms
5 ms
8 ms
7 ms
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.

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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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 - 25 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.

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

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. 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) - Mobile

Currently Not Available

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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

Your page has 1 blocking script resources and 4 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.Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:,300italic,400,400italic,600,600italic,700,700italic,800,800italic%7CMerriweather:300,300italic,400,400italic,700,700italic,900,900italic

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 56.1KiB (65% reduction).

Compressing could save 56.1KiB (65% reduction).

Optimize images

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

Optimize the following images to reduce their size by 35.7KiB (44% reduction).

Compressing could save 21.9KiB (35% reduction).
Compressing and resizing could save 13.8KiB (75% 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 9.6KiB (33% reduction).

Minifying could save 9.6KiB (33% reduction) after compression.

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 3.4KiB (30% reduction).

Minifying could save 1.8KiB (67% reduction) after compression.
Minifying could save 1.7KiB (19% reduction) after compression.
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.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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: 17.99 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 supports HTTPS
Verifying SSL Support. Please wait...
Common Name:
Issuer: Let's Encrypt Authority X3
Valid from: Nov 13 17:25:32 2019 GMT
Valid until: Feb 11 17:25:32 2020 GMT

+ Verify HTTP/2 Support supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sun, 24 Nov 2019 18:11:04 GMT
Connection: close
Server: Netlify
Cache-Control: no-store
Content-Type: text/html
Content-Language: en
Content-Length: 220

+ DNS Lookup

Type Ip Target TTL
SOA 3600
Serial Number 2019111406
Refresh 3600
Retry 900
Expire 1209600
Minimum TTL 0
TXT 600
TXT 600
TXT 600
MX 3600
MX 3600
MX 3600
MX 3600
MX 3600
A 3571
NS 3568
NS 3568

+ Whois Lookup

Domain Created:
Domain Age:

whois lookup at
Requests of this client are not permitted. Please use for queries.
Last update was 126 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
28 secs
1 min
1 min
1 min
2 mins
2 mins
2 mins
2 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