Outagereport.In - Info outagereport.in

outagereport.in receives about 764 unique visitors and 764 (1.00 per visitor) page views per day which should earn about $3.12/day from advertising revenue. Estimated site value is $1,251.96. According to Alexa Traffic Rank outagereport.in is ranked number 1,116,623 in the world and 4.5E-5% of global Internet users visit it. Site is hosted in United States and links to network IP address 104.31.78.97. This server supports HTTPS and HTTP/2.

About - outagereport.in


Technologies used on Website

UI frameworks
Bootstrap
CDN
CloudFlare
Web Frameworks
Express
Web Servers
Express
Font Scripts
Font Awesome
Google Font API
Advertising
Google AdSense
Analytics
Google Analytics
JavaScript Frameworks
React
Programming Languages
Node.js

outagereport.in Profile

Last update was 288 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is outagereport.in?

764 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
764
Monthly Unique Visitors:
18,336
Pages per Visit:
1.00
Daily Pageviews:
764
Alexa Rank:
1,116,623 visit alexa
Alexa Reach:
4.5E-5%   (of global internet users)
Avg. visit duration:
02:42
Bounce rate:
61.51%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
3.83%
Referral:
15.34%
Search:
80.83%
Social:
0%
Paid:
0%

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  outagereport.in
Rank:
(Rank based on keywords, cost and organic traffic)
  1,700,024
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
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 outagereport.in?

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:
outagereport.in
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:
outagereport.in
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 outagereport.in can earn?

Daily Revenue:
$3.12
Monthly Revenue:
$93.60
Yearly Revenue:
$1,138.80
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do outagereport.in lose due to Adblock?

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

Daily revenue loss by country

Currently Not Available

How much is outagereport.in worth?

Website Value:
$1,251.96

+ Where is outagereport.in hosted?

Server IP:
104.31.78.97
ASN:
AS13335 
ISP:
Cloudflare Inc 
Server Location:

United States, US
 

Other sites hosted on 104.31.78.97

+ How fast does outagereport.in load?

Average Load Time:
(4923 ms) 9 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

92
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

Max Potential First Input Delay 140 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 4.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
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 120 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 3090 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.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 4.2 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 1.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 1.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://outagereport.in/
0 ms150 ms0 KB0 KB301text/html
http://outagereport.in/amp
150 ms283 ms5 KB18 KB200text/htmlDocument
https://fonts.googleapis.com/css?family=Roboto:400,500,700
293 ms337 ms1 KB7 KB200text/cssStylesheet
https://cdn.ampproject.org/v0.js
293 ms338 ms73 KB269 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-ad-0.1.js
293 ms339 ms19 KB61 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-analytics-0.1.js
297 ms340 ms41 KB146 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-iframe-0.1.js
297 ms340 ms9 KB21 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-live-list-0.1.js
297 ms341 ms8 KB20 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-image-lightbox-0.1.js
297 ms341 ms10 KB30 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-bind-0.1.js
298 ms342 ms16 KB45 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-list-0.1.js
298 ms342 ms12 KB33 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-social-share-0.1.js
298 ms343 ms7 KB16 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-sidebar-0.1.js
298 ms343 ms6 KB15 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-accordion-0.1.js
298 ms343 ms6 KB14 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-form-0.1.js
298 ms343 ms15 KB43 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-selector-0.1.js
298 ms344 ms4 KB9 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-consent-0.1.js
298 ms345 ms11 KB32 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-geo-0.1.js
299 ms346 ms5 KB7 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-sticky-ad-1.0.js
299 ms346 ms4 KB7 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-mustache-0.2.js
299 ms346 ms13 KB33 KB200text/javascriptScript
https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css
295 ms339 ms7 KB30 KB200text/cssStylesheet
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
352 ms378 ms11 KB11 KB200font/woff2Font
https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
353 ms405 ms76 KB75 KB200font/woff2Font
http://outagereport.in/img/logo-small.png
454 ms531 ms5 KB5 KB200image/pngImage
https://cdn.ampproject.org/rtv/011907301630320/ww.js
473 ms532 ms14 KB46 KB200text/javascriptFetch
https://d-23248548771396313494.ampproject.net/1907301630320/frame.html
541 ms577 ms1 KB0 KB200text/htmlOther
https://3p.ampproject.net/1907301630320/f.js
541 ms578 ms53 KB165 KB200text/javascriptOther
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
542 ms579 ms35 KB94 KB200text/javascriptOther
blob:http://outagereport.in/033574f1-24b4-4a91-a9d5-3bc9061e5555
573 ms578 ms0 KB46 KB200text/javascriptOther
https://cdn.ampproject.org/rtv/011907301630320/v0/amp-crypto-polyfill-0.1.js
609 ms618 ms5 KB9 KB200text/javascriptScript
https://www.google-analytics.com/r/collect?v=1&_v=a1&ds=AMP&aip&_s=1&dt=Outage%20Report%20India&sr=412x660&_utmht=1565791638800&cid=amp-_F0rygAM-2KAUSWVOS5aHw&tid=UA-91909045-1&dl=http%3A%2F%2Foutagereport.in%2Famp&dr=&sd=24&ul=en-us&de=UTF-8&t=pageview&jid=0.12651666591731736&_r=1&a=5670&z=0.7527651125494534
610 ms619 ms0 KB0 KB-1Other
Uses efficient cache policy on static assets - 1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://outagereport.in/img/logo-small.png
31536000 ms5 KB
Third-Party Usage - 4 Third-Parties Found
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 Time
279 KB700 ms
83 KB0 ms
35 KB0 ms
0 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
306 ms
6 ms
313 ms
8 ms
368 ms
16 ms
399 ms
67 ms
472 ms
7 ms
480 ms
14 ms
506 ms
7 ms
512 ms
7 ms
520 ms
5 ms
525 ms
7 ms
533 ms
8 ms
541 ms
7 ms
564 ms
12 ms
590 ms
5 ms
603 ms
28 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.

URL
Potential Savings
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
26 ms
https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
52 ms
JavaScript execution time - 0.7 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
636 ms217 ms3 ms
https://cdn.ampproject.org/v0.js
468 ms401 ms33 ms
Remove unused CSS - Potential savings of 7 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.

URL
SizePotential Savings
https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css
7 KB7 KB
Avoids enormous network payloads - Total size was 474 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
76 KB
https://cdn.ampproject.org/v0.js
73 KB
https://3p.ampproject.net/1907301630320/f.js
53 KB
https://cdn.ampproject.org/v0/amp-analytics-0.1.js
41 KB
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
35 KB
https://cdn.ampproject.org/v0/amp-ad-0.1.js
19 KB
https://cdn.ampproject.org/v0/amp-bind-0.1.js
16 KB
https://cdn.ampproject.org/v0/amp-form-0.1.js
15 KB
https://cdn.ampproject.org/rtv/011907301630320/ww.js
14 KB
https://cdn.ampproject.org/v0/amp-mustache-0.2.js
13 KB
Minimizes main-thread work - 1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
761 ms
Other
239 ms
Style & Layout
149 ms
Script Parsing & Compilation
126 ms
Parse HTML & CSS
38 ms
Rendering
23 ms
Avoids an excessive DOM size - 109 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](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
109
Maximum DOM Depth
16
Maximum Child Elements
9
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://outagereport.in/)
0
http://outagereport.in/amp
630
User Timing marks and measures - 7 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Name
TypeStart TimeDuration
is
Mark404 ms0 ms
e_is
Mark432 ms0 ms
visible
Mark440 ms0 ms
ofv
Mark440 ms0 ms
mbv
Mark445 ms0 ms
pc
Mark565 ms0 ms
ol
Mark565 ms0 ms
Keep request counts low and transfer sizes small - 31 requests • 474 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
31474 KB
Script
18265 KB
Other
7104 KB
Font
287 KB
Stylesheet
29 KB
Image
15 KB
Document
15 KB
Media
00 KB
Third-party
28463 KB
Eliminate render-blocking resources - Potential savings of 780 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
https://fonts.googleapis.com/css?family=Roboto:400,500,700
1 KB780
https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css
7 KB780
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.

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.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Serve images in next-gen formats
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.

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

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. 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 130 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.

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

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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

Your page has 1 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:

https://fonts.googleapis.com/css?family=Roboto:400,500,700

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="https://outage.report/">Outage Report</a> and 5 others are close to other tap targets .

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Reduce server response time

In our test, your server responded in 0.37 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

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:

https://cdn.ampproject.org/v0/amp-geo-0.1.js (30 minutes)
https://cdn.ampproject.org/v0.js (50 minutes)
http://outagereport.in/img/logo-small.png (8.8 hours)

Optimize images

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

Optimize the following images to reduce their size by 1.4KiB (28% reduction).

Compressing http://outagereport.in/img/logo-small.png could save 1.4KiB (28% reduction).
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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.
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.
Enable compression
You have compression enabled. Learn more about enabling compression.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does outagereport.in use compression?

outagereport.in does not use compression.
Original size: 91.8 KB
Compressed size: n/a
File reduced by: n/a

+ 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

outagereport.in supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: sni189190.cloudflaressl.com
Organization:
Location:
Issuer: COMODO ECC Domain Validation Secure Server CA 2
Valid from: Jul 27 00:00:00 2019 GMT
Valid until: Feb 2 23:59:59 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

outagereport.in supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Wed, 14 Aug 2019 14:07:03 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=df16509b4da06ca72c66ce26f7604b1ba1565791623; expires=Thu, 13-Aug-20 14:07:03 GMT; path=/; domain=.outagereport.in; HttpOnly
Server: cloudflare
CF-RAY: 50637e30baa1c63b-MSP

+ DNS Lookup

Type Ip Target TTL
HINFO 3600
NS zelda.ns.cloudflare.com 3600
NS jeremy.ns.cloudflare.com 3600

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.inregistry.net...
\Error - could not open a connection to whois.inregistry.net
Last update was 288 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with outagereport.in 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!
outagereport.in widget