Johnhammond.Org - Info receives about 17 unique visitors and 34 (2.00 per visitor) page views per day which should earn about $0.14/day from advertising revenue. Estimated site value is $58.17. According to Alexa Traffic Rank is ranked number 11,102,228 in the world and 1.0E-6% of global Internet users visit it. Site is hosted in North Bergen, New Jersey, 07047, United States and links to network IP address This server supports HTTPS and doesn't support HTTP/2.

About -

Technologies used on Website

Currently Not Available Profile

Title: John Hammond
Last update was 31 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

17 daily visitors
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
11,102,228 visit alexa
Alexa Reach:
1.0E-6%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources


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)

On October 30 SEMrush is hosting first of a kind 24-hour online conference for marketers around the globe — Global Marketing Day. The event is designed for marketers to learn from the most successful in the field. Speakers from Google, Walt Disney, Adobe, BBC, WeWork, and many more will share real cases, tools and insights, so attendees can find out more about marketing in a day than many do by slaving over books for months. This unique experience is absolutely free!
Sign up & watch for free >>

+ 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:
DigitalOcean, LLC 
Server Location:
North Bergen
New Jersey, NJ
United States, US

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

Speed Index 1.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.9 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.9 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.9 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.

Remove unused CSS - Potential savings of 2 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
3 KB2 KB
Avoids enormous network payloads - Total size was 845 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

95 KB
84 KB
83 KB
55 KB
46 KB
36 KB
34 KB
32 KB
32 KB
30 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.

Time Spent
Script Evaluation
928 ms
195 ms
Script Parsing & Compilation
69 ms
Style & Layout
53 ms
Parse HTML & CSS
41 ms
Garbage Collection
22 ms
19 ms
Serve images in next-gen formats - Potential savings of 29 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
31 KB16 KB
18 KB13 KB
Avoids an excessive DOM size - 68 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
Preload key requests - Potential savings of 850 ms
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Potential Savings
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 - 69 requests • 845 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
69845 KB
25574 KB
19118 KB
395 KB
942 KB
611 KB
74 KB
00 KB
59601 KB
Eliminate render-blocking resources - Potential savings of 290 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
95 KB190
Enable text compression - Potential savings of 63 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

SizePotential Savings
95 KB62 KB
2 KB1 KB
Efficiently encode images - Potential savings of 5 KB
Optimized images load faster and consume less cellular data. Learn more.

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

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms71 ms0 KB0 KB301text/html
71 ms139 ms2 KB3 KB200text/htmlDocument
150 ms216 ms3 KB2 KB200text/cssStylesheet
150 ms346 ms95 KB95 KB200application/javascriptScript
151 ms283 ms22 KB22 KB200image/jpegImage
151 ms165 ms36 KB96 KB200text/javascriptScript
166 ms419 ms8 KB8 KB200image/pngImage
284 ms541 ms19 KB18 KB200image/pngImage
379 ms504 ms1 KB2 KB200application/javascriptScript
384 ms454 ms34 KB33 KB200application/font-sfntFont
384 ms455 ms7 KB6 KB200application/font-sfntFont
384 ms566 ms55 KB54 KB200application/font-sfntFont
435 ms446 ms1 KB0 KB200application/javascriptScript
438 ms464 ms84 KB222 KB200text/javascriptScript
451 ms475 ms83 KB222 KB200text/javascriptScript
475 ms484 ms8 KB17 KB200text/htmlDocument
535 ms583 ms46 KB128 KB200application/javascriptScript
609 ms792 ms7 KB11 KB200text/htmlDocument
616 ms626 ms29 KB77 KB200text/javascriptScript
643 ms792 ms7 KB10 KB200text/htmlDocument
677 ms685 ms1 KB0 KB200text/htmlDocument
707 ms725 ms1 KB2 KB200application/jsonScript
782 ms798 ms30 KB97 KB200application/javascriptScript
814 ms821 ms1 KB0 KB200image/gifImage
814 ms821 ms2 KB2 KB200text/javascriptScript
815 ms823 ms30 KB78 KB200text/javascriptScript
816 ms821 ms6 KB12 KB200text/javascriptScript
821 ms851 ms1 KB0 KB200text/htmlDocument
823 ms854 ms13 KB24 KB200text/javascriptScript
824 ms829 ms4 KB7 KB200text/javascriptScript
825 ms832 ms1 KB0 KB200image/gifImage
825 ms830 ms2 KB2 KB200text/javascriptScript
925 ms933 ms30 KB78 KB200text/javascriptScript
955 ms960 ms6 KB12 KB200text/javascriptScript
891 ms905 ms3 KB8 KB200text/cssStylesheet
892 ms911 ms1 KB1 KB200text/cssStylesheet
910 ms924 ms3 KB8 KB200text/cssStylesheet
910 ms923 ms1 KB1 KB200text/cssStylesheet
914 ms954 ms1 KB3 KB200text/cssStylesheet
961 ms971 ms1 KB0 KB200text/htmlDocument
961 ms988 ms12 KB23 KB200text/javascriptScript
970 ms979 ms12 KB30 KB200text/javascriptScript
973 ms983 ms15 KB41 KB200text/javascriptScript
973 ms980 ms32 KB31 KB200image/jpegImage
973 ms1017 ms1 KB0 KB200image/gifImage
990 ms1030 ms1 KB0 KB302text/html
991 ms1017 ms1 KB0 KB302text/html
1002 ms1002 ms32 KB31 KB200image/jpegImage
1003 ms1004 ms12 KB30 KB200text/javascriptScript
1006 ms1006 ms15 KB41 KB200text/javascriptScript
1007 ms1040 ms1 KB0 KB200image/gifImage
1017 ms1163 ms1 KB0 KB200image/gifImage
1029 ms1038 ms9 KB22 KB200text/htmlDocument
1029 ms1054 ms1 KB0 KB302text/html
1029 ms1062 ms1 KB0 KB302text/html
1030 ms1103 ms1 KB0 KB302
1042 ms1053 ms9 KB22 KB200text/htmlDocument
1054 ms1126 ms1 KB0 KB302
1062 ms1204 ms1 KB0 KB200image/gifImage
1103 ms1211 ms1 KB0 KB200image/gifImage
1126 ms1164 ms1 KB0 KB200image/gifImage
1134 ms1134 ms0 KB0 KB200image/pngImage
1142 ms1142 ms0 KB0 KB200image/pngImage
1187 ms1198 ms6 KB12 KB200text/javascriptScript
1189 ms1198 ms6 KB12 KB200text/javascriptScript!oKOlo7tE7jDksvfgTZYCAAABClIAAABvmQGuD7r8NCe22D5WALFM03AHotHCvF9RpMxwkFrQVQ5ftZCUKtBWM0n_JkDBf-oPZ7yIFMw-hgUDPej97sNIn_uCTJrNIF1IeonRLkucH8dZ5BUfs6fxdPil6pBAFVjSy-cfAJHBcqr13XY1KkBpEt_A4hjU9CVzqfdUyT7fb5vU_Pw7FDzdYemCLn29cnGldZ9NdfH-0MaH9HU8NchU0kQya9O4znx1MzR2aVdGfl2vRGIPdXj0f14_lvjn8y5cNxF-YC-3ema3-tua7ZuBoABBBpW4KlNVJLTlaig3GCzUqMnlNYVfjW_MD1MNYAtwPvGMURrqHdFX2UfHZBqIdzth7YYtTwoduGD0RwmwkN8JFjchROiX3UHsy26G85gjnqeBgE6qklSjWbfBYrRfviGS0pSOdWd1YfbWwolzcc_FrrrbKnFsPvTBcAjvBpeH4DgnNmkNMny6wkHeQIMeLgv_3wDEvbtTlqOGMGXeBWR4t0WReqAt2jzK16lIzfZ9Zqv4yw8Q1jqfqe_Tt1TJHkadSThzkyg8MPdJYhqj4TbDoc42RO6aSdGqCw9BagXAQQ
1589 ms1596 ms1 KB0 KB204image/gifImage!fX6lfmZEp2BrE7IWtLACAAAA-1IAAABfmQGu0aQIo7HL3LtmVA3l0kbdxCXn7J3PQsPfyiZyNzNBQTqLqOEZMcXOgucaqHgw6NhSzfkBHw1BSsG249c1hxwG_iHRmzDocPqw8fuIJ9QLrgRBQ83ZGSmhMCotqMjEGtcMnHfXB9vHJW5fm3EYO7NrvaxkyCbFAHw8RRdIqFLcU-qtl_BRE8Slpk2au8XrMB4b7aS7xaD-HHInYoEg8cxnZ8-6trJebSzDyODX-R5FFkHkjq5U2p14eafuUKA-BqQhTpPzEQHhZ0hJHYKsv1ggL4ksxnFUjMJdctnEqO6dy9SnE7gLbTCHl1W-7666LLSEchqfxJck6T-46KvpKgR7vdMoGPmhce8VwCG5ZR9XWdx_-xh8aXf8jcWaTqK6ACzIdPLjJEzxSrRQYPh8U2KNAdFZdfvVulDGkPxxC-T0WSms8RkPZHqXyqGzv6QYuIQiEouuwUaq_lXNyt4uS9CVgBHZvpLTy7QnvrcQ-cWFpKldOWxb_r_1MAb0DlPQaiYO1-AsixQE1bsBjne-XPuE2j1LB_LQ3STqhGB0tjwVmAxkz-SG-dLBgA5E0Yo4SQ
1601 ms1607 ms1 KB0 KB204image/gifImage,1081,1081,1081,1081&tos=1081,0,0,0,0&p=150,101,750,221&mcvt=1081&rs=1&ht=0&tfs=217&tls=1298&mc=1<e=1&bas=0&bac=0&met=0&avms=nio&niot_obs=39&niot_cbk=53&md=2&lm=2&rst=1568558610469&dlt=185&rpt=155&isd=0&msd=0&oseid=3&xdi=0&ps=800%2C868&ss=800%2C600&pt=695&bin=1&deb=1-3-3-19-12-47-69-10-0-0-0&tvt=1268&r=v&id=osdim&vs=4&uc=16&upc=7&tgt=DIV&cl=1&cec=1&clc=1&cac=1&cd=0x0&itpl=20&v=20190913
2026 ms2035 ms1 KB0 KB200image/gifImage,1081,1081,1081,1081&tos=1081,0,0,0,0&p=150,101,750,221&mcvt=1081&rs=1&ht=0&tfs=217&tls=1298&mc=1<e=1&bas=0&bac=0&met=0&avms=nio&niot_obs=39&niot_cbk=53&md=2&lm=2&rst=1568558610469&dlt=185&rpt=155&isd=0&msd=0&oseid=3&xdi=0&ps=800%2C868&ss=800%2C600&pt=695&bin=1&deb=1-3-3-19-12-47-69-10-0-0-0&tvt=1268&r=v&id=osdim&vs=4&uc=8&upc=7&tgt=DIV&cl=1&cec=1&clc=1&cac=1&cd=0x0&itpl=20&v=20190913
2032 ms2045 ms1 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 24 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
0 ms46 KB
0 ms30 KB
0 ms3 KB
0 ms3 KB
0 ms1 KB
0 ms1 KB
0 ms1 KB
285000 ms1 KB
1800000 ms1 KB
43200000 ms95 KB
43200000 ms55 KB
43200000 ms34 KB
43200000 ms22 KB
43200000 ms19 KB
43200000 ms8 KB
43200000 ms7 KB
43200000 ms3 KB
1209600000 ms12 KB
1209600000 ms12 KB
1209600000 ms6 KB
1209600000 ms6 KB
1209600000 ms4 KB
1209600000 ms2 KB
1209600000 ms2 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.

SizeMain Thread Time
511 KB502 ms
86 KB134 ms
2 KB0 ms
1 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
162 ms
7 ms
373 ms
56 ms
432 ms
92 ms
534 ms
6 ms
542 ms
7 ms
556 ms
6 ms
567 ms
71 ms
646 ms
21 ms
671 ms
16 ms
689 ms
40 ms
730 ms
7 ms
737 ms
53 ms
815 ms
7 ms
823 ms
7 ms
834 ms
10 ms
850 ms
88 ms
938 ms
5 ms
946 ms
7 ms
958 ms
5 ms
972 ms
10 ms
985 ms
11 ms
1002 ms
6 ms
1014 ms
5 ms
1020 ms
15 ms
1039 ms
10 ms
1051 ms
13 ms
1065 ms
5 ms
1075 ms
7 ms
1084 ms
5 ms
1090 ms
6 ms
1097 ms
19 ms
1116 ms
7 ms
1128 ms
17 ms
1149 ms
7 ms
1158 ms
6 ms
1179 ms
7 ms
1186 ms
6 ms
1220 ms
28 ms
1250 ms
12 ms
1262 ms
45 ms
1312 ms
7 ms
1319 ms
12 ms
1335 ms
12 ms
1351 ms
12 ms
1364 ms
14 ms
1382 ms
7 ms
1389 ms
13 ms
1404 ms
9 ms
1419 ms
12 ms
1431 ms
6 ms
1439 ms
12 ms
1452 ms
12 ms
1464 ms
13 ms
1477 ms
13 ms
1503 ms
14 ms
1524 ms
36 ms
1561 ms
16 ms
1581 ms
21 ms
1601 ms
10 ms
1612 ms
11 ms
1623 ms
6 ms
1935 ms
5 ms
2043 ms
5 ms
2049 ms
5 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
71 ms
71 ms
182 ms
JavaScript execution time - 0.9 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
637 ms359 ms7 ms
128 ms107 ms6 ms
120 ms110 ms4 ms
113 ms108 ms4 ms
75 ms66 ms7 ms
52 ms25 ms2 ms
50 ms46 ms4 ms
Properly size images - Potential savings of 45 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
22 KB20 KB
18 KB18 KB
8 KB7 KB
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.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. 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 70 ms
Time To First Byte identifies the time at which your server sends a response. 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.

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.

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 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.Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:

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) (5 minutes) (30 minutes) (50 minutes) (60 minutes) (12 hours) (12 hours) (12 hours) (12 hours) (12 hours)

Optimize images

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

Optimize the following images to reduce their size by 119.7KiB (40% reduction).

Compressing could save 91.7KiB (38% reduction).
Compressing and resizing could save 17.1KiB (92% reduction).
Compressing could save 7.5KiB (32% reduction).
Compressing could save 2.5KiB (25% reduction).
Compressing could save 1,012B (17% reduction).

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Graphic Design and 3 others render only 7 pixels tall (19 CSS pixels) .
If you want to…competitions. and 13 others render only 6 pixels tall (16 CSS pixels) .
yours renders only 6 pixels tall (16 CSS pixels) .
(just kidding) renders only 5 pixels tall (13 CSS pixels) .
body renders only 6 pixels tall (16 CSS pixels) .
YouTube and 1 others render only 6 pixels tall (16 CSS pixels) .
résumé and 1 others render only 5 pixels tall (13 CSS pixels) .

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

Compressing could save 62KiB (65% reduction).
Compressing could save 1.4KiB (63% reduction).

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="/programming">Programming</a> and 3 others are close to other tap targets .

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 1.4KiB (25% reduction).

Minifying could save 682B (30% reduction).
Minifying could save 428B (18% reduction) after compression.
Minifying could save 295B (32% reduction) after compression.

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 102B (15% reduction).

Minifying could save 102B (15% reduction) after compression.
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.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 3.39 KB
Compressed size: 1.67 KB
File reduced by: 1.72 KB (50%)

+ 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: Aug 10 20:47:33 2019 GMT
Valid until: Nov 8 20:47:33 2019 GMT
Authority: Is not a CA
Common Name: Let's Encrypt Authority X3
Organization: Let's Encrypt
Location: US
Issuer: DST Root CA X3
Valid from: Mar 17 16:40:46 2016 GMT
Valid until: Mar 17 16:40:46 2021 GMT
Authority: Is a CA
Keysize: 2048 Bits

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

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx/1.10.3 (Ubuntu)
Date: Sun, 15 Sep 2019 14:43:06 GMT
Content-Type: text/html
Content-Length: 194
Connection: keep-alive

HTTP/1.1 200 OK
Server: nginx/1.10.3 (Ubuntu)
Date: Sun, 15 Sep 2019 14:43:06 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: flag="FLAG{even_in_the_cookies}"; Path=/
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
SOA 1800
Serial Number 1532023995
Refresh 10800
Retry 3600
Expire 604800
Minimum TTL 0
A 3600
NS 1800
NS 1800
NS 1800

+ Whois Lookup

Domain Created:
Domain Age:
4 years 6 months  

whois lookup at
Registry Domain ID: D175627805-LROR
Registrar WHOIS Server:
Registrar URL:
Updated Date: 2019-03-16T15:26:35Z
Creation Date: 2015-03-15T02:49:10Z
Registry Expiry Date: 2021-03-15T02:49:10Z
Registrar Registration Expiration Date:
Registrar:, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientDeleteProhibited
Domain Status: clientRenewProhibited
Domain Status: clientTransferProhibited
Domain Status: clientUpdateProhibited
Registrant Organization: Domains By Proxy, LLC
Registrant State/Province: Arizona
Registrant Country: US
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form
>>> Last update of WHOIS database: 2019-09-15T14:42:37Z <<<

For more information on Whois status codes, please visit

Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no cir***stances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Last update was 31 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.

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