Zwischentoene.Info - Info receives about 34 unique visitors and 34 (1.00 per visitor) page views per day which should earn about $0.14/day from advertising revenue. Estimated site value is $58.42. According to Alexa Traffic Rank is ranked number 8,595,757 in the world and 2.0E-6% of global Internet users visit it. Site is hosted in Soest, North Rhine-Westphalia, 59494, Germany and links to network IP address This server doesn't support HTTPS and doesn't support HTTP/2.

About -

Technologies used on Website

Web Servers
Font Scripts
Google Font API
Programming Languages
Operating Systems
Ubuntu Profile

Title: zwischentöne: Themen
Description: Vielfalt im Klassenzimmer ist der Normalfall. Die Webplattform Zwischentöne bietet Anregungen, wie die Auseinandersetzung mit gesellschaftlicher Vielfalt im Unterricht gelingen kann. Die Unterrichtsmodule für die Fächer Politik, Geschichte und Ethik/Religion der Sekundarstufen I und II widmen sich Fragen, die in Schulbüchern oft zu kurz kommen. Dabei geht es nicht vorrangig darum, zusätzliche Informationen über "neue" Themen anzubieten. Vielmehr bieten die Unterrichtsmodule "neue" Perspektiven auf Themen, die in der Migrationsgesellschaft Deutschland zwar allgegenwärtig sind, aber im Unterricht selten behandelt werden.
Keywords: Unterrichtsmaterialien, Module, Vielfalt, Diversität, Diversity, Migration, Religion, Islam, Muslime, Identität
Last update was 146 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

34 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
8,595,757 visit alexa
Alexa Reach:
2.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)

+ 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:
Verein zur Foerderung eines Deutschen Forschungsnetzes e.V. 
Server Location:
North Rhine-Westphalia, NW
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

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 20 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.
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.
Speed Index 1.3 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.

Screenshot Thumbnails

This is what the load of your site looked like.

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

Resource Type
RequestsTransfer Size
27275 KB
8105 KB
581 KB
773 KB
511 KB
15 KB
10 KB
00 KB
11140 KB
Eliminate render-blocking resources - Potential savings of 80 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
2 KB190|Bitter:400|Open+Sans:400,400italic,600
1 KB190
1 KB190
1 KB190
7 KB230
3 KB190
1 KB190
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms283 ms0 KB0 KB307text/html
283 ms1269 ms5 KB12 KB200text/htmlDocument
1280 ms1523 ms2 KB6 KB200text/cssStylesheet|Bitter:400|Open+Sans:400,400italic,600
1280 ms1313 ms1 KB9 KB200text/cssStylesheet
1281 ms1297 ms1 KB1 KB200text/cssStylesheet
1281 ms1299 ms1 KB1 KB200text/cssStylesheet
1281 ms1527 ms7 KB26 KB200text/cssStylesheet
1281 ms1526 ms3 KB5 KB200application/javascriptScript
1282 ms1523 ms1 KB1 KB200application/javascriptScript
1282 ms1647 ms21 KB21 KB200image/jpegImage
1282 ms1643 ms27 KB26 KB200image/jpegImage
1532 ms1773 ms25 KB25 KB200image/jpegImage
1531 ms1538 ms33 KB91 KB200text/javascriptScript
1532 ms1778 ms10 KB29 KB200application/javascriptScript
1532 ms1774 ms3 KB10 KB200application/javascriptScript
1532 ms1784 ms0 KB0 KB200application/javascriptScript
1535 ms1766 ms9 KB9 KB200image/jpegImage
1536 ms1770 ms15 KB15 KB200image/jpegImage
1537 ms2007 ms8 KB8 KB200image/pngImage
1538 ms1543 ms29 KB28 KB200font/woff2Font
1540 ms1543 ms9 KB9 KB200font/woff2Font
1541 ms1545 ms14 KB14 KB200font/woff2Font
1542 ms1545 ms13 KB13 KB200font/woff2Font
1543 ms1546 ms15 KB15 KB200font/woff2Font
1576 ms2134 ms23 KB66 KB200application/javascriptScript
1794 ms1920 ms0 KB0 KB404text/htmlImage>_ms=986&pv_id=EJeYzn
2160 ms2437 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 14 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
0 ms27 KB
0 ms25 KB
0 ms23 KB
0 ms21 KB
0 ms15 KB
0 ms10 KB
0 ms9 KB
0 ms8 KB
0 ms7 KB
0 ms3 KB
0 ms3 KB
0 ms2 KB
0 ms1 KB
0 ms0 KB
Third-Party Usage - 1 Third-Party 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
33 KB34 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1290 ms
6 ms
1551 ms
42 ms
1610 ms
10 ms
1621 ms
21 ms
1804 ms
15 ms
2158 ms
22 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
4 ms
4 ms
4 ms
3 ms
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
112 ms2 ms1 ms
Remove unused CSS - Potential savings of 5 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
7 KB5 KB
Avoids enormous network payloads - Total size was 275 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

33 KB
29 KB
27 KB
25 KB
23 KB
21 KB
15 KB
15 KB
14 KB
13 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
54 ms
Style & Layout
52 ms
45 ms
Parse HTML & CSS
9 ms
Script Parsing & Compilation
9 ms
7 ms
Serve images in next-gen formats - Potential savings of 43 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
26 KB12 KB
15 KB11 KB
25 KB11 KB
21 KB10 KB
Avoids an excessive DOM size - 98 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
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
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.

Reduce server response times (TTFB) - Root document took 990 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.

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.

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

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 2 blocking script resources and 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.Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:|Bitter:400|Open+Sans:400,400italic,600;text=t%C3%B6ne;text=%3C%3E

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.

Materialien fü…Klassenzimmer and 2 others render only 6 pixels tall (16 CSS pixels) .
THEMEN renders only 5 pixels tall (14 CSS pixels) .
PROJEKT renders only 5 pixels tall (14 CSS pixels) .
AUTOR_INNEN and 2 others render only 5 pixels tall (14 CSS pixels) .
18 UNTERRICHTSMODULE and 2 others render only 5 pixels tall (12 CSS pixels) .
Deutsch zu sei…chaft ergeben. and 2 others render only 5 pixels tall (14 CSS pixels) .
AKTUELL renders only 8 pixels tall (20 CSS pixels) .
Projekttreffen…ountdown läuft renders only 6 pixels tall (16 CSS pixels) .
Auf dem sechst…s der durch... renders only 6 pixels tall (16 CSS pixels) .
zum Archiv -&gt; and 1 others render only 6 pixels tall (16 CSS pixels) .
Nutzungsbed. and 5 others render only 5 pixels tall (14 CSS pixels) .
gefördert (2013-2016): renders only 5 pixels tall (14 CSS pixels) .

Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,098 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <span class="site-tagline dimmed no-print">Materialien fü…Klassenzimmer</span> falls outside the viewport.
The element <img src="/fileadmin/use…haft-small.jpg"> falls outside the viewport.
The element <h1>Religionen &amp; W…n glauben wir?</h1> falls outside the viewport.
The element <aside class="meta-data dimmed">10 Unterrichtsmodule</aside> falls outside the viewport.
The element <p>„Die“ Muslime…n unterliegen.</p> falls outside the viewport.
The element <h2>Aktuell</h2> falls outside the viewport.
The element <div class="news-tsr">14.05.2019…zum Archiv -&gt;</div> falls outside the viewport.
The element <a href="" class="ir footer-logo-rbs">Robert-Bosch-Stiftung</a> falls outside the viewport.

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.

Reduce server response time

In our test, your server responded in 0.22 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: (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified)

Optimize images

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

Optimize the following images to reduce their size by 18.4KiB (22% reduction).

Compressing could save 6.3KiB (24% reduction).
Compressing could save 5.4KiB (23% reduction).
Compressing could save 4.5KiB (22% reduction).
Compressing could save 2.2KiB (15% 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="/news/newsdeta…wn-laeuft.html">Projekttreffen…ountdown läuft</a> is close to 1 other tap targets .
The tap target <a href="/news.html">zum Archiv -&gt;</a> is close to 1 other tap targets .
The tap target <a href="/twitter.html">Twitter</a> and 1 others are close to other tap targets .

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 1.2KiB (44% reduction).

Minifying could save 1.1KiB (46% reduction) after compression.
Minifying could save 104B (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 878B (21% reduction).

Minifying could save 878B (21% 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 482B (33% reduction).

Minifying could save 482B (33% 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.
Enable compression
You have compression enabled. Learn more about enabling compression.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 11.76 KB
Compressed size: 4.23 KB
File reduced by: 7.53 KB (64%)

+ 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

Date: Sun, 22 Sep 2019 21:55:04 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Powered-By: PHP/5.5.9-1ubuntu4.29
Content-Length: 0
Content-Type: text/html

HTTP/1.1 200 OK
Date: Sun, 22 Sep 2019 21:55:04 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Powered-By: PHP/5.5.9-1ubuntu4.29
Cache-Control: private
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 4336
Content-Type: text/html; charset=utf-8

+ DNS Lookup

Type Ip Target TTL
A 3600
SOA 2560
Serial Number 2019081312
Refresh 16384
Retry 2048
Expire 1048576
Minimum TTL 0
MX 3600
NS 3567
NS 3567

+ Whois Lookup

Domain Created:
Domain Age:
7 years 23 days  

whois lookup at
Registry Domain ID: D47638204-LRMS
Registrar WHOIS Server:
Registrar URL:
Updated Date: 2019-07-31T11:18:42Z
Creation Date: 2012-08-30T09:39:09Z
Registry Expiry Date: 2020-08-30T09:39:09Z
Registrar Registration Expiration Date:
Registrar: Mesh Digital Limited
Registrar IANA ID: 1390
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: ok
Registrant Organization: Georg-Eckert-Institut fuer internationale Schulbuchforschung
Registrant State/Province: unknown
Registrant Country: DE
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form is
>>> Last update of WHOIS database: 2019-09-22T21:54:39Z <<<

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 146 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
17 secs
21 secs
40 secs
1 min
1 min
1 min
1 min
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