Inmagazine.Info - Info receives about 272 unique visitors and 272 (1.00 per visitor) page views per day which should earn about $1.11/day from advertising revenue. Estimated site value is $810.65. According to Alexa Traffic Rank is ranked number 4,823,425 in the world and 6.0E-6% of global Internet users visit it. Site is hosted in Germany and links to network IP address This server supports HTTPS and doesn't support HTTP/2.

About -

Technologies used on Website

Google AdSense
Font Scripts
Google Font API
JavaScript Libraries
jQuery Migrate
Yoast SEO
Programming Languages
MySQL Profile

Title: News - In Magazine
Last update was 124 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

272 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
4,823,425 visit alexa
Alexa Reach:
6.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:
Hetzner Online GmbH 
Server Location:

Germany, DE

Other sites hosted on

+ How fast does load?

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

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

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 6.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 6.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 3.2 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 3.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 230 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 8.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 470 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 70 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) 6077 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

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

SizePotential Savings
47 KB47 KB
17 KB17 KB
16 KB16 KB
14 KB14 KB
12 KB12 KB
10 KB10 KB
8 KB8 KB
5 KB5 KB
2 KB2 KB
Remove unused CSS - Potential savings of 15 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
19 KB15 KB
Avoids enormous network payloads - Total size was 867 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

92 KB
86 KB
84 KB
53 KB
47 KB
41 KB
38 KB
38 KB
33 KB
30 KB
Minimize main-thread work - 3.5 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
1868 ms
Style & Layout
625 ms
459 ms
Script Parsing & Compilation
196 ms
183 ms
Parse HTML & CSS
123 ms
Serve images in next-gen formats - Potential savings of 58 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
92 KB35 KB
47 KB13 KB
41 KB9 KB
Avoids an excessive DOM size - 365 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
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

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

Resource Type
RequestsTransfer Size
45867 KB
16390 KB
16375 KB
645 KB
528 KB
128 KB
10 KB
00 KB
13273 KB
Eliminate render-blocking resources - Potential savings of 2,040 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
5 KB330
10 KB780
0 KB480
2 KB480
9 KB780
19 KB1080
33 KB930
4 KB180
38 KB930
18 KB480
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms699 ms0 KB0 KB301text/html
699 ms1167 ms11 KB50 KB200text/htmlDocument
1182 ms1298 ms5 KB29 KB200text/cssStylesheet
1182 ms1303 ms10 KB39 KB200text/cssStylesheet
1182 ms1291 ms0 KB0 KB200text/cssStylesheet
1183 ms1291 ms2 KB6 KB200text/cssStylesheet
1184 ms1298 ms9 KB68 KB200text/cssStylesheet
1184 ms1406 ms19 KB102 KB200text/cssStylesheet
1184 ms1403 ms33 KB95 KB200application/javascriptScript
1184 ms1294 ms4 KB10 KB200application/javascriptScript
1185 ms1404 ms38 KB108 KB200application/javascriptScript
1185 ms1399 ms18 KB63 KB200application/javascriptScript
1185 ms1202 ms38 KB103 KB200text/javascriptScript
1185 ms1212 ms28 KB73 KB200application/javascriptScript
1465 ms1483 ms3 KB2 KB200image/jpegImage
1465 ms1574 ms14 KB13 KB200image/pngImage
1465 ms2091 ms86 KB86 KB200image/jpegImage
1465 ms1809 ms92 KB92 KB200image/jpegImage
1465 ms1699 ms41 KB41 KB200image/jpegImage
1465 ms1584 ms11 KB11 KB200image/jpegImage
1465 ms1574 ms12 KB12 KB200image/jpegImage
1466 ms1886 ms8 KB8 KB200image/jpegImage
1466 ms1573 ms5 KB5 KB200image/jpegImage
1466 ms1586 ms10 KB10 KB200image/jpegImage
1466 ms1575 ms14 KB14 KB200image/jpegImage
1466 ms1684 ms17 KB17 KB200image/jpegImage
1466 ms1577 ms16 KB16 KB200image/jpegImage
1467 ms1780 ms47 KB47 KB200image/jpegImage
1467 ms1577 ms12 KB12 KB200image/jpegImage
1237 ms1363 ms3 KB7 KB200application/javascriptScript
1237 ms1456 ms20 KB79 KB200application/javascriptScript
1364 ms1641 ms1 KB2 KB200application/javascriptScript
1459 ms1567 ms1 KB1 KB200application/javascriptScript
1467 ms1887 ms5 KB14 KB200application/javascriptScript
1480 ms2012 ms28 KB50 KB200font/woffFont
1597 ms1608 ms1 KB0 KB200application/javascriptScript
1600 ms1625 ms84 KB220 KB200text/javascriptScript
1618 ms1626 ms7 KB15 KB200text/htmlDocument
1644 ms1652 ms18 KB43 KB200text/javascriptScript!0&fsb=1&dtd=115
1720 ms1884 ms7 KB32 KB200text/htmlDocument
1722 ms1731 ms30 KB78 KB200text/javascriptScript>m=2ouav9&z=452556993
1752 ms1757 ms1 KB0 KB200image/gifImage
1912 ms1930 ms53 KB142 KB200text/javascriptScript!1&btvi=1&fsb=1&xpc=FrlR7FfOsy&p=https%3A//
2086 ms2236 ms1 KB0 KB200text/htmlDocument!2&btvi=2&fsb=1&xpc=HFjLLf8hki&p=https%3A//
2089 ms2230 ms1 KB0 KB200text/htmlDocument
Serve static assets with an efficient cache policy - 32 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
0 ms92 KB
0 ms86 KB
0 ms47 KB
0 ms41 KB
0 ms38 KB
0 ms33 KB
0 ms28 KB
0 ms20 KB
0 ms19 KB
0 ms18 KB
0 ms17 KB
0 ms16 KB
0 ms14 KB
0 ms14 KB
0 ms12 KB
0 ms12 KB
0 ms11 KB
0 ms10 KB
0 ms10 KB
0 ms9 KB
0 ms8 KB
0 ms5 KB
0 ms5 KB
0 ms5 KB
0 ms4 KB
0 ms3 KB
0 ms2 KB
0 ms1 KB
0 ms1 KB
0 ms0 KB
300000 ms3 KB
7200000 ms18 KB
Reduce the impact of third-party code - Third-party code blocked the main thread for 440 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
224 KB415 ms
19 KB25 ms
28 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1196 ms
8 ms
1208 ms
53 ms
1438 ms
22 ms
1470 ms
14 ms
1486 ms
10 ms
1496 ms
109 ms
1605 ms
38 ms
1643 ms
6 ms
1662 ms
9 ms
1672 ms
6 ms
1678 ms
16 ms
1698 ms
52 ms
1758 ms
22 ms
1782 ms
16 ms
1813 ms
38 ms
1856 ms
5 ms
1913 ms
7 ms
1927 ms
7 ms
1940 ms
116 ms
2058 ms
5 ms
2069 ms
19 ms
2091 ms
5 ms
2097 ms
32 ms
2260 ms
8 ms
2268 ms
8 ms
2282 ms
19 ms
2305 ms
9 ms
2317 ms
6 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
532 ms
Reduce JavaScript execution time - 2.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
1244 ms60 ms19 ms
796 ms636 ms41 ms
398 ms315 ms13 ms
195 ms186 ms8 ms
152 ms127 ms21 ms
137 ms119 ms8 ms
127 ms101 ms18 ms
85 ms78 ms5 ms
80 ms61 ms7 ms
69 ms59 ms10 ms
63 ms54 ms9 ms
Minify CSS - Potential savings of 5 KB
Minifying CSS files can reduce network payload sizes. Learn more.

SizePotential Savings
19 KB5 KB
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.

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

Avoid chaining critical requests - 15 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.

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 470 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.

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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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)***6x522.jpg (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) (5 minutes) (15 minutes) (50 minutes) (60 minutes)******ytics.js (2 hours)

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:

Optimize images

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

Optimize the following images to reduce their size by 68.6KiB (45% reduction).

Compressing and resizing***6x522.jpg could save 43.3KiB (92% reduction).
Compressing could save 21.9KiB (24% reduction).
Compressing could save 2.6KiB (20% reduction).
Compressing could save 735B (32% reduction).

Reduce server response time

In our test, your server responded in 0.31 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.

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 5.9KiB (21% reduction).

Minifying could save 3.5KiB (19% reduction) after compression.
Minifying could save 2.3KiB (26% reduction) after compression.

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 1.5KiB (15% reduction).

Minifying could save 1.5KiB (15% 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.
Enable compression
You have compression enabled. Learn more about enabling compression.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
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? use gzip compression.
Original size: 270.99 KB
Compressed size: 34.72 KB
File reduced by: 236.27 KB (87%)

+ 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 20 23:54:11 2019 GMT
Valid until: Feb 18 23:54:11 2020 GMT

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

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sun, 24 Nov 2019 19:28:05 GMT
X-Redirect-By: WordPress
Vary: User-Agent
Content-Length: 0
Content-Type: text/html; charset=UTF-8
X-Varnish: 17056931
Age: 0
X-Cache: MISS
Connection: keep-alive

HTTP/1.1 200 OK
Date: Sun, 24 Nov 2019 19:28:05 GMT
Vary: Accept-Encoding,User-Agent
Content-Encoding: gzip
Content-Length: 35549
Content-Type: text/html; charset=UTF-8
X-Varnish: 19498976
Age: 0
X-Cache: MISS
Accept-Ranges: bytes
Connection: keep-alive

+ DNS Lookup

Type Ip Target TTL
MX 3557
A 3557
SOA 3557
Serial Number 2019101000
Refresh 3600
Retry 1800
Expire 1209600
Minimum TTL 0
TXT 3557
NS 3557
NS 3557

+ Whois Lookup

Domain Created:
Domain Age:
2 months 4 days  

whois lookup at
Registry Domain ID: D503300001168126679-LRMS
Registrar WHOIS Server:
Registrar URL:
Updated Date: 2019-11-19T20:32:25Z
Creation Date: 2019-09-20T10:18:07Z
Registry Expiry Date: 2020-09-20T10:18:07Z
Registrar Registration Expiration Date:
Registrar: NameCheap, Inc
Registrar IANA ID: 1068
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: clientTransferProhibited
Registrant Organization: WhoisGuard, Inc.
Registrant State/Province: Panama
Registrant Country: PA
Name Server: NS16.ZEMI.MK
Name Server: NS15.ZEMI.MK
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form is
>>> Last update of WHOIS database: 2019-11-24T19:27:45Z <<<

For more information on Whois status codes, please visit

Access to AFILIAS WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Afilias registry database. The data in this record is provided by Afilias Limited for informational purposes only, and Afilias 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. Afilias 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 124 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
0 secs
21 secs
47 secs
50 secs
1 min
2 mins
2 mins
3 mins
4 mins
4 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