Intimes-Niedersachsen.Biz - Info intimes-niedersachsen.biz

intimes-niedersachsen.biz receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank intimes-niedersachsen.biz is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in Germany and links to network IP address 157.97.34.124. This server doesn't support HTTPS and doesn't support HTTP/2.

About - intimes-niedersachsen.biz


Technologies used on Website

Web Servers
Apache
Analytics
Google Analytics
Programming Languages
PHP

intimes-niedersachsen.biz Profile

Title: Willkommen bei Intimes-Niedersachsen.de - Dem erotischen Telefonbuch für Niedersachsen.
Description: Das erotische Telefonbuch
Keywords: Erotik,Deutschland,Niedersachsen,Girls,Dessous,Fotos,Model,Modelle,Modelle aus Niedersachsen,Bad M???nder,Bad Nenndorf,Bad Pyrmont,Barsinghausen,Braunschweig,Bremen,Brilon,Diepenau,Diepholz,Garbsen-Berenbostel,G???ttingen,Hameln,Hannover,Hannover Laatzen,Hannover Langenhagen,Hannover Mitte,Hannover Nord,Hannover Ost,Hannover S???d,Hannover West,Heemsen,Hildesheim,Kassel,Laatzen,Lingen,M???nster,Oldenburg,Osnabr???ck,Porta Westfalica,Rheine,Rodenberg,Ronnenberg,Seelze,Seesen,Twistringen,Wagenfeld,Wallenhorst,Wolfenb???ttel,Wolfsburg
Last update was 12 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is intimes-niedersachsen.biz?

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
 n/a
Monthly Unique Visitors:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
00:00
Bounce rate:
n/a
*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

SEMrush
Domain:
  intimes-niedersachsen.biz
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
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 intimes-niedersachsen.biz?

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:
intimes-niedersachsen.biz
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:
intimes-niedersachsen.biz
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 intimes-niedersachsen.biz can earn?

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

Daily earning by country

Currently Not Available

How much money do intimes-niedersachsen.biz 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 intimes-niedersachsen.biz worth?

Website Value:
n/a

+ Where is intimes-niedersachsen.biz hosted?

Server IP:
157.97.34.124
ASN:
AS15817 
ISP:
Mittwald CM Service GmbH und Co.KG 
Server Location:

Germany, DE
 

Other sites hosted on 157.97.34.124

+ How fast does intimes-niedersachsen.biz load?

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

Page Speed (Google PageSpeed Insights) - Desktop

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST 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.

First Contentful Paint (FCP)984ms 76% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 76% 21% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 21% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
First Input Delay (FID)6ms 100% of loads for this page have a fast (<100ms) First Input Delay (FID) 100% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an FAST 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.

First Contentful Paint (FCP)771ms 86% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 86% 12% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 12% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)9ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.7 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.7 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.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
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.7 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.

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

URL
SizePotential Savings
http://www.intimes-niedersachsen.de/startseite/head_banner.png
5 KB2 KB
Avoids enormous network payloads - Total size was 82 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.intimes-niedersachsen.de/startseite/main.jpg
21 KB
http://www.intimes-niedersachsen.de/startseite/head.jpg
18 KB
http://www.google-analytics.com/ga.js
17 KB
http://www.intimes-niedersachsen.de/
9 KB
http://www.intimes-niedersachsen.de/startseite/head_banner.png
6 KB
http://www.owl-intim.de/gif/ci_button.gif
5 KB
http://www.owl-intim.de/gif/jusprog.png
2 KB
http://www.owl-intim.de/gif/icra_sw.gif
2 KB
http://www.google-analytics.com/__utm.gif?utmwv=5.7.2&utms=2&utmn=233129670&utmhn=www.intimes-niedersachsen.de&utmcs=windows-1252&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Willkommen%20bei%20Intimes-Niedersachsen.de%20-%20Dem%20erotischen%20Telefonbuch%20f%C3%BCr%20Niedersachsen.&utmhid=995040945&utmr=-&utmp=%2F&utmht=1573293206021&utmac=UA-4909505-1&utmcc=__utma%3D197369335.1050755829.1573293206.1573293206.1573293206.1%3B%2B__utmz%3D197369335.1573293206.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=&utmmt=1&utmu=vAAAAAAAAAAAAAAAAAAAAAAE~
0 KB
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=1096327595&utmhn=www.intimes-niedersachsen.de&utmcs=windows-1252&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Willkommen%20bei%20Intimes-Niedersachsen.de%20-%20Dem%20erotischen%20Telefonbuch%20f%C3%BCr%20Niedersachsen.&utmhid=995040945&utmr=-&utmp=%2F&utmht=1573293206006&utmac=UA-22121760-3&utmcc=__utma%3D197369335.1050755829.1573293206.1573293206.1573293206.1%3B%2B__utmz%3D197369335.1573293206.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=799977798&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAAAAAAE~
0 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
44 ms
Other
22 ms
Style & Layout
15 ms
Script Parsing & Compilation
8 ms
Rendering
7 ms
Parse HTML & CSS
4 ms
Avoids an excessive DOM size - 86 elements
A large DOM will 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
86
Maximum DOM Depth
21
Maximum Child Elements
11
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://intimes-niedersachsen.biz/)
0
http://www.intimes-niedersachsen.de/
190
Keep request counts low and transfer sizes small - 11 requests • 82 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
1182 KB
Image
855 KB
Script
117 KB
Document
19 KB
Other
10 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Third-party
728 KB
Enable text compression - Potential savings of 6 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://www.intimes-niedersachsen.de/
9 KB6 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://intimes-niedersachsen.biz/
0 ms331 ms0 KB0 KB301text/html
http://www.intimes-niedersachsen.de/
332 ms775 ms9 KB9 KB200text/htmlDocument
http://www.owl-intim.de/gif/icra_sw.gif
786 ms999 ms2 KB2 KB200image/gifImage
http://www.owl-intim.de/gif/jusprog.png
786 ms999 ms2 KB2 KB200image/pngImage
http://www.owl-intim.de/gif/ci_button.gif
788 ms1131 ms5 KB5 KB200image/gifImage
http://www.intimes-niedersachsen.de/startseite/head_banner.png
788 ms897 ms6 KB5 KB200image/pngImage
http://www.google-analytics.com/ga.js
789 ms793 ms17 KB45 KB200text/javascriptScript
http://www.intimes-niedersachsen.de/startseite/head.jpg
792 ms1208 ms18 KB18 KB200image/jpegImage
http://www.intimes-niedersachsen.de/startseite/main.jpg
792 ms901 ms21 KB21 KB200image/jpegImage
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=1096327595&utmhn=www.intimes-niedersachsen.de&utmcs=windows-1252&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Willkommen%20bei%20Intimes-Niedersachsen.de%20-%20Dem%20erotischen%20Telefonbuch%20f%C3%BCr%20Niedersachsen.&utmhid=995040945&utmr=-&utmp=%2F&utmht=1573293206006&utmac=UA-22121760-3&utmcc=__utma%3D197369335.1050755829.1573293206.1573293206.1573293206.1%3B%2B__utmz%3D197369335.1573293206.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=799977798&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAAAAAAE~
840 ms847 ms0 KB0 KB200image/gifImage
http://www.google-analytics.com/__utm.gif?utmwv=5.7.2&utms=2&utmn=233129670&utmhn=www.intimes-niedersachsen.de&utmcs=windows-1252&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Willkommen%20bei%20Intimes-Niedersachsen.de%20-%20Dem%20erotischen%20Telefonbuch%20f%C3%BCr%20Niedersachsen.&utmhid=995040945&utmr=-&utmp=%2F&utmht=1573293206021&utmac=UA-4909505-1&utmcc=__utma%3D197369335.1050755829.1573293206.1573293206.1573293206.1%3B%2B__utmz%3D197369335.1573293206.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=&utmmt=1&utmu=vAAAAAAAAAAAAAAAAAAAAAAE~
854 ms858 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 7 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://www.intimes-niedersachsen.de/startseite/main.jpg
0 ms21 KB
http://www.intimes-niedersachsen.de/startseite/head.jpg
0 ms18 KB
http://www.intimes-niedersachsen.de/startseite/head_banner.png
0 ms6 KB
http://www.owl-intim.de/gif/ci_button.gif
0 ms5 KB
http://www.owl-intim.de/gif/jusprog.png
0 ms2 KB
http://www.owl-intim.de/gif/icra_sw.gif
0 ms2 KB
http://www.google-analytics.com/ga.js
7200000 ms17 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
18 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
803 ms
7 ms
816 ms
18 ms
839 ms
41 ms
881 ms
7 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.

URL
Total CPU TimeScript EvaluationScript Parse
Other
51 ms3 ms1 ms
Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

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

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

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.

Avoid chaining critical requests - 1 chain 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 440 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. 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.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. 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.


Page Speed (Google PageSpeed Insights) - Mobile

97
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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.

First Contentful Paint (FCP)618ms 76% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 90% 7% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 7% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)268ms 1% of loads for this page have a fast (<100ms) First Input Delay (FID) 1% 97% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 97% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%

Origin Data

All pages served from this origin have an AVERAGE 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.

First Contentful Paint (FCP)702ms 88% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 88% 9% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 9% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)273ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 2% 96% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 96% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 2.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 170 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 2.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint (3G) 4157 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. 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 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 2.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.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 2.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 86 elements
A large DOM will 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
86
Maximum DOM Depth
21
Maximum Child Elements
11
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://intimes-niedersachsen.biz/)
0
http://www.intimes-niedersachsen.de/
630
Keep request counts low and transfer sizes small - 11 requests • 82 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
1182 KB
Image
855 KB
Script
117 KB
Document
19 KB
Other
10 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Third-party
728 KB
Enable text compression - Potential savings of 6 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://www.intimes-niedersachsen.de/
9 KB6 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://intimes-niedersachsen.biz/
0 ms331 ms0 KB0 KB301text/html
http://www.intimes-niedersachsen.de/
331 ms784 ms9 KB9 KB200text/htmlDocument
http://www.owl-intim.de/gif/icra_sw.gif
794 ms1173 ms2 KB2 KB200image/gifImage
http://www.owl-intim.de/gif/jusprog.png
794 ms1126 ms2 KB2 KB200image/pngImage
http://www.owl-intim.de/gif/ci_button.gif
796 ms1316 ms5 KB5 KB200image/gifImage
http://www.intimes-niedersachsen.de/startseite/head_banner.png
796 ms1217 ms6 KB5 KB200image/pngImage
http://www.google-analytics.com/ga.js
797 ms803 ms17 KB45 KB200text/javascriptScript
http://www.intimes-niedersachsen.de/startseite/head.jpg
799 ms1214 ms18 KB18 KB200image/jpegImage
http://www.intimes-niedersachsen.de/startseite/main.jpg
799 ms1011 ms21 KB21 KB200image/jpegImage
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=1548262193&utmhn=www.intimes-niedersachsen.de&utmcs=windows-1252&utmsr=412x660&utmvp=980x1569&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Willkommen%20bei%20Intimes-Niedersachsen.de%20-%20Dem%20erotischen%20Telefonbuch%20f%C3%BCr%20Niedersachsen.&utmhid=2133684797&utmr=-&utmp=%2F&utmht=1573293200179&utmac=UA-22121760-3&utmcc=__utma%3D197369335.1482010239.1573293200.1573293200.1573293200.1%3B%2B__utmz%3D197369335.1573293200.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=981354275&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAAAAAAE~
853 ms857 ms0 KB0 KB200image/gifImage
http://www.google-analytics.com/__utm.gif?utmwv=5.7.2&utms=2&utmn=1620321293&utmhn=www.intimes-niedersachsen.de&utmcs=windows-1252&utmsr=412x660&utmvp=980x1569&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Willkommen%20bei%20Intimes-Niedersachsen.de%20-%20Dem%20erotischen%20Telefonbuch%20f%C3%BCr%20Niedersachsen.&utmhid=2133684797&utmr=-&utmp=%2F&utmht=1573293200192&utmac=UA-4909505-1&utmcc=__utma%3D197369335.1482010239.1573293200.1573293200.1573293200.1%3B%2B__utmz%3D197369335.1573293200.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=&utmmt=1&utmu=vAAAAAAAAAAAAAAAAAAAAAAE~
864 ms868 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 7 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://www.intimes-niedersachsen.de/startseite/main.jpg
0 ms21 KB
http://www.intimes-niedersachsen.de/startseite/head.jpg
0 ms18 KB
http://www.intimes-niedersachsen.de/startseite/head_banner.png
0 ms6 KB
http://www.owl-intim.de/gif/ci_button.gif
0 ms5 KB
http://www.owl-intim.de/gif/jusprog.png
0 ms2 KB
http://www.owl-intim.de/gif/icra_sw.gif
0 ms2 KB
http://www.google-analytics.com/ga.js
7200000 ms17 KB
Minimize third-party usage - Third-party code blocked the main thread for 60 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.

Third-Party
SizeMain-Thread Blocking Time
18 KB59 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
805 ms
6 ms
817 ms
20 ms
842 ms
42 ms
884 ms
7 ms
JavaScript execution time - 0.2 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
207 ms10 ms4 ms
http://www.google-analytics.com/ga.js
143 ms121 ms22 ms
http://www.intimes-niedersachsen.de/
54 ms50 ms2 ms
Avoids enormous network payloads - Total size was 82 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.intimes-niedersachsen.de/startseite/main.jpg
21 KB
http://www.intimes-niedersachsen.de/startseite/head.jpg
18 KB
http://www.google-analytics.com/ga.js
17 KB
http://www.intimes-niedersachsen.de/
9 KB
http://www.intimes-niedersachsen.de/startseite/head_banner.png
6 KB
http://www.owl-intim.de/gif/ci_button.gif
5 KB
http://www.owl-intim.de/gif/jusprog.png
2 KB
http://www.owl-intim.de/gif/icra_sw.gif
2 KB
http://www.google-analytics.com/__utm.gif?utmwv=5.7.2&utms=2&utmn=1620321293&utmhn=www.intimes-niedersachsen.de&utmcs=windows-1252&utmsr=412x660&utmvp=980x1569&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Willkommen%20bei%20Intimes-Niedersachsen.de%20-%20Dem%20erotischen%20Telefonbuch%20f%C3%BCr%20Niedersachsen.&utmhid=2133684797&utmr=-&utmp=%2F&utmht=1573293200192&utmac=UA-4909505-1&utmcc=__utma%3D197369335.1482010239.1573293200.1573293200.1573293200.1%3B%2B__utmz%3D197369335.1573293200.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=&utmmt=1&utmu=vAAAAAAAAAAAAAAAAAAAAAAE~
0 KB
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=1548262193&utmhn=www.intimes-niedersachsen.de&utmcs=windows-1252&utmsr=412x660&utmvp=980x1569&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Willkommen%20bei%20Intimes-Niedersachsen.de%20-%20Dem%20erotischen%20Telefonbuch%20f%C3%BCr%20Niedersachsen.&utmhid=2133684797&utmr=-&utmp=%2F&utmht=1573293200179&utmac=UA-22121760-3&utmcc=__utma%3D197369335.1482010239.1573293200.1573293200.1573293200.1%3B%2B__utmz%3D197369335.1573293200.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=981354275&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAAAAAAE~
0 KB
Minimizes main-thread work - 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
181 ms
Other
83 ms
Style & Layout
73 ms
Script Parsing & Compilation
28 ms
Rendering
24 ms
Parse HTML & CSS
15 ms
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 450 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. 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.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. 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.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

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.

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

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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.

Erotikführers…tlich verhält, and 5 others render only 4 pixels tall (10 CSS pixels) .
Intimes-Niedersachsen.de renders only 4 pixels tall (10 CSS pixels) .
Verlassen and 2 others render only 5 pixels tall (12 CSS pixels) .
Unsere Seiten…1024x768 Pixel and 1 others render only 5 pixels tall (12 CSS pixels) .
City-Intim - E…ür Deutschland and 9 others render only 5 pixels tall (12 CSS pixels) .

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="http://www.owl…/impressum.htm">Impressum</a> is close to 1 other tap targets .
The tap target <a href="http://www.rotelaterne.de">Rote Laterne</a> and 7 others are close to other tap targets .
The tap target <a href="http://www.icra.org/sitelabel"></a> and 2 others are close to other tap targets .

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.

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:

http://www.intimes-niedersachsen.de/startseite/head.jpg (expiration not specified)
http://www.intimes-niedersachsen.de/startseite/head_banner.png (expiration not specified)
http://www.intimes-niedersachsen.de/startseite/main.jpg (expiration not specified)
http://www.owl-intim.de/gif/ci_button.gif (expiration not specified)
http://www.owl-intim.de/gif/icra_sw.gif (expiration not specified)
http://www.owl-intim.de/gif/jusprog.png (expiration not specified)
http://www.google-***ytics.com/ga.js (2 hours)

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 6.1KiB (68% reduction).

Compressing http://www.intimes-niedersachsen.de/ could save 6.1KiB (68% reduction).

Optimize images

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

Optimize the following images to reduce their size by 3.1KiB (16% reduction).

Compressing http://www.intimes-niedersachsen.de/startseite/head.jpg could save 2.4KiB (14% reduction).
Compressing http://www.owl-intim.de/gif/icra_sw.gif could save 648B (40% reduction).

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.6KiB (18% reduction).

Minifying http://www.intimes-niedersachsen.de/ could save 1.6KiB (18% reduction).
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.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
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.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does intimes-niedersachsen.biz use compression?

intimes-niedersachsen.biz does not use compression.
Original size: 8.93 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

intimes-niedersachsen.biz does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

intimes-niedersachsen.biz does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sat, 09 Nov 2019 09:53:07 GMT
Server: Apache
Location: http://www.intimes-niedersachsen.de
Content-Length: 243
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 101 Switching Protocols
Upgrade: h2c
Connection: Upgrade

HTTP/2 200 
date: Thu, 01 Jan 1970 00:00:00 GMT
server: Apache
x-powered-by: PHP/5.2.11
content-type: text/html

+ DNS Lookup

Type Ip Target TTL
SOA 3575
Mname dns.typo3server.com
Rname support.mittwald.de
Serial Number 1901220001
Refresh 28800
Retry 7200
Expire 604800
Minimum TTL 0
MX mx1.agenturserver.de 3575
MX mx2.agenturserver.de 3575
MX mx3.agenturserver.de 3575
MX mx4.agenturserver.de 3575
AAAA 3575
A 157.97.34.124 3575
NS ns3.dnsmittwald.de 3570
NS dns.typo3server.com 3570
NS ns2.typo3server.com 3570

+ Whois Lookup

Domain Created:
2010-06-25
Domain Age:
9 years 4 months 14 days  
WhoIs:
 

whois lookup at whois.biz...
Domain Name: intimes-niedersachsen.biz
Registry Domain ID: D40173903-BIZ
Registrar WHOIS Server: whois.1api.net
Registrar URL: www.1api.net
Updated Date: 2019-01-19T11:29:12Z
Creation Date: 2010-06-25T09:50:27Z
Registry Expiry Date: 2020-06-24T23:59:59Z
Registrar: 1API GmbH
Registrar IANA ID: 1387
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +49.6841***84200
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name:
Registrant Organization:
Registrant Street:
Registrant Street:
Registrant Street:
Registrant City:
Registrant State/Province:
Registrant Postal Code:
Registrant Country: DE
Registrant Phone:
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID:
Admin Name:
Admin Organization:
Admin Street:
Admin Street:
Admin Street:
Admin City:
Admin State/Province:
Admin Postal Code:
Admin Country:
Admin Phone:
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID:
Tech Name:
Tech Organization:
Tech Street:
Tech Street:
Tech Street:
Tech City:
Tech State/Province:
Tech Postal Code:
Tech Country:
Tech Phone:
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: dns.typo3server.com
Name Server: ns2.typo3server.com
Name Server: ns3.dnsmittwald.de
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-11-09T09:53:30Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

The above WHOIS results have been redacted to remove potential personal data. The full WHOIS output may be available to individuals and organisations with a legitimate interest in accessing this data not outweighed by the fundamental privacy rights of the data subject. To find out more, or to make a request for access, please visit: RDDSrequest.nic.biz.

NeuStar, Inc., the Registry Operator for .BIZ, has collected this information for the WHOIS database through an ICANN-Accredited Registrar. This information is provided to you for informational purposes only and is designed to assist persons in determining contents of a domain name registration record in the NeuStar registry database. NeuStar makes this information available to you "as is" and does not guarantee its accuracy. By submitting a WHOIS query, you agree that you will use this data only for lawful purposes and that, under no cir***stances will you use this data: (1) to allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone; (2) in contravention of any applicable data and privacy protection acts; or (3) to enable high volume, automated, electronic processes that apply to the registry (or its systems). Compilation, repackaging, dissemination, or other use of the WHOIS database in its entirety, or of a substantial portion thereof, is not allowed without NeuStar's prior written permission. NeuStar reserves the right to modify or change these conditions at any time without prior or subsequent notification of any kind. By executing this query, in any manner whatsoever, you agree to abide by these terms.
Last update was 12 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

primecc.su
35 secs
econbank.com.br
44 secs
rukomarine.com
1 min
ecoagro.agr.br
1 min
tangysoft.net
2 mins
ecoa.org.br
2 mins
toystore.live
2 mins
tangtang2vs.com
3 mins
cdaction.pl
3 mins
ecgiordano.com.br
3 mins

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!
intimes-niedersachsen.biz widget