Lendenmann.Org - Info lendenmann.org

lendenmann.org receives about 17 unique visitors and 17 (1.00 per visitor) page views per day which should earn about $0.07/day from advertising revenue. Estimated site value is $31.73. According to Alexa Traffic Rank lendenmann.org is ranked number 18,021,303 in the world and 1.0E-6% of global Internet users visit it. Site is hosted in Zurich, Zurich, 8008, Switzerland and links to network IP address 46.140.22.212. This server doesn't support HTTPS and doesn't support HTTP/2.

About - lendenmann.org


lendenmann.org Profile

Title: Jürg Lendenmann – Texte
Last update was 3 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is lendenmann.org?

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

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
0%
Referral:
100.00%
Search:
0%
Social:
0%
Paid:
0%

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  lendenmann.org
Rank:
(Rank based on keywords, cost and organic traffic)
  12,543,706
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

Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

How socially engaged is lendenmann.org?

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:
lendenmann.org
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:
lendenmann.org
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 lendenmann.org can earn?

Daily Revenue:
$0.07
Monthly Revenue:
$2.10
Yearly Revenue:
$25.55
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do lendenmann.org 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 lendenmann.org worth?

Website Value:
$31.73

Where is lendenmann.org hosted?

Server IP:
46.140.22.212
ASN:
AS6830 
ISP:
Liberty Global Operations B.V. 
Server Location:
Zurich
Zurich, ZH
8008
Switzerland, CH
 

Other sites hosted on 46.140.22.212

There are no other sites hosted on this IP

How fast does lendenmann.org load?

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

Page Speed (Google PageSpeed Insights) - Desktop

100
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

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 0.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.3 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.3 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.3 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.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 27 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.google-analytics.com/ga.js
17 KB
http://lendenmann.org/
3 KB
http://lendenmann.org/images/bu_pa_man_2015.png
2 KB
http://lendenmann.org/Library/jlxhtml.css
2 KB
https://cse.google.com/coop/cse/brand?form=cse-search-box&lang=de
2 KB
https://www.google.com/cse/static/images/1x/googlelogo_lightgrey_46x16dp.png
1 KB
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=952601426&utmhn=lendenmann.org&utmcs=UTF-8&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=J%C3%BCrg%20Lendenmann%20%E2%80%93%20Texte&utmhid=341114734&utmr=-&utmp=%2F&utmht=1562936666601&utmac=UA-3831576-1&utmcc=__utma%3D88035717.1460774760.1562936667.1562936667.1562936667.1%3B%2B__utmz%3D88035717.1562936667.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=74073501&utmredir=1&utmu=HAAAAAAAAAAAAAAAAAAAAAAE~
0 KB
http://www.google.com/coop/cse/brand?form=cse-search-box&lang=de
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.

Category
Time Spent
Script Evaluation
36 ms
Style & Layout
22 ms
Other
17 ms
Rendering
7 ms
Parse HTML & CSS
4 ms
Script Parsing & Compilation
3 ms
Avoids an excessive DOM size - 58 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
58
Maximum DOM Depth
6
Maximum Child Elements
9
Keep request counts low and transfer sizes small - 8 requests • 27 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
827 KB
Script
219 KB
Image
34 KB
Document
13 KB
Stylesheet
12 KB
Other
10 KB
Media
00 KB
Font
00 KB
Third-party
520 KB
Eliminate render-blocking resources - Potential savings of 60 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://lendenmann.org/Library/jlxhtml.css
2 KB70
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://lendenmann.org/
0 ms138 ms3 KB6 KB200text/htmlDocument
http://lendenmann.org/Library/jlxhtml.css
151 ms317 ms2 KB1 KB200text/cssStylesheet
http://lendenmann.org/images/bu_pa_man_2015.png
151 ms317 ms2 KB2 KB200image/pngImage
http://www.google.com/coop/cse/brand?form=cse-search-box&lang=de
151 ms319 ms0 KB0 KB302text/html
https://cse.google.com/coop/cse/brand?form=cse-search-box&lang=de
319 ms350 ms2 KB3 KB200text/javascriptScript
http://www.google-analytics.com/ga.js
355 ms361 ms17 KB45 KB200text/javascriptScript
https://www.google.com/cse/static/images/1x/googlelogo_lightgrey_46x16dp.png
374 ms407 ms1 KB1 KB200image/pngImage
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=952601426&utmhn=lendenmann.org&utmcs=UTF-8&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=J%C3%BCrg%20Lendenmann%20%E2%80%93%20Texte&utmhid=341114734&utmr=-&utmp=%2F&utmht=1562936666601&utmac=UA-3831576-1&utmcc=__utma%3D88035717.1460774760.1562936667.1562936667.1562936667.1%3B%2B__utmz%3D88035717.1562936667.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=74073501&utmredir=1&utmu=HAAAAAAAAAAAAAAAAAAAAAAE~
401 ms407 ms0 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://lendenmann.org/images/bu_pa_man_2015.png
0 ms2 KB
http://lendenmann.org/Library/jlxhtml.css
0 ms2 KB
https://cse.google.com/coop/cse/brand?form=cse-search-box&lang=de
1800000 ms2 KB
http://www.google-analytics.com/ga.js
7200000 ms17 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
161 ms
6 ms
340 ms
22 ms
387 ms
37 ms
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.

JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. 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.

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

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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 140 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.


Page Speed (Google PageSpeed Insights) - Mobile

93
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 4.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.5 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.8 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.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 100 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 1.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Contentful Paint (3G) 1560 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.

Avoids enormous network payloads - Total size was 27 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.google-analytics.com/ga.js
17 KB
http://lendenmann.org/
3 KB
http://lendenmann.org/images/bu_pa_man_2015.png
2 KB
http://lendenmann.org/Library/jlxhtml.css
2 KB
https://cse.google.com/coop/cse/brand?form=cse-search-box&lang=de
2 KB
https://www.google.com/cse/static/images/1x/googlelogo_lightgrey_46x16dp.png
1 KB
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=952601426&utmhn=lendenmann.org&utmcs=UTF-8&utmsr=412x660&utmvp=412x660&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=J%C3%BCrg%20Lendenmann%20%E2%80%93%20Texte&utmhid=341114734&utmr=-&utmp=%2F&utmht=1562936662516&utmac=UA-3831576-1&utmcc=__utma%3D88035717.1385742788.1562936663.1562936663.1562936663.1%3B%2B__utmz%3D88035717.1562936663.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=74073501&utmredir=1&utmu=HAAAAAAAAAAAAAAAAAAAAAAE~
0 KB
http://www.google.com/coop/cse/brand?form=cse-search-box&lang=de
0 KB
Minimizes main-thread work - 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
107 ms
Style & Layout
69 ms
Other
62 ms
Parse HTML & CSS
13 ms
Script Parsing & Compilation
11 ms
Rendering
10 ms
Avoids an excessive DOM size - 58 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
58
Maximum DOM Depth
6
Maximum Child Elements
9
Keep request counts low and transfer sizes small - 8 requests • 27 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
827 KB
Script
219 KB
Image
34 KB
Document
13 KB
Stylesheet
12 KB
Other
10 KB
Media
00 KB
Font
00 KB
Third-party
520 KB
Eliminate render-blocking resources - Potential savings of 150 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://lendenmann.org/Library/jlxhtml.css
2 KB180
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://lendenmann.org/
0 ms2539 ms3 KB6 KB200text/htmlDocument
http://lendenmann.org/Library/jlxhtml.css
2549 ms2912 ms2 KB1 KB200text/cssStylesheet
http://lendenmann.org/images/bu_pa_man_2015.png
2549 ms2912 ms2 KB2 KB200image/pngImage
http://www.google.com/coop/cse/brand?form=cse-search-box&lang=de
2549 ms2914 ms0 KB0 KB302text/html
https://cse.google.com/coop/cse/brand?form=cse-search-box&lang=de
2914 ms2949 ms2 KB3 KB200text/javascriptScript
http://www.google-analytics.com/ga.js
2953 ms2963 ms17 KB45 KB200text/javascriptScript
https://www.google.com/cse/static/images/1x/googlelogo_lightgrey_46x16dp.png
2953 ms2970 ms1 KB1 KB200image/pngImage
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=952601426&utmhn=lendenmann.org&utmcs=UTF-8&utmsr=412x660&utmvp=412x660&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=J%C3%BCrg%20Lendenmann%20%E2%80%93%20Texte&utmhid=341114734&utmr=-&utmp=%2F&utmht=1562936662516&utmac=UA-3831576-1&utmcc=__utma%3D88035717.1385742788.1562936663.1562936663.1562936663.1%3B%2B__utmz%3D88035717.1562936663.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=74073501&utmredir=1&utmu=HAAAAAAAAAAAAAAAAAAAAAAE~
2990 ms2996 ms0 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://lendenmann.org/images/bu_pa_man_2015.png
0 ms2 KB
http://lendenmann.org/Library/jlxhtml.css
0 ms2 KB
https://cse.google.com/coop/cse/brand?form=cse-search-box&lang=de
1800000 ms2 KB
http://www.google-analytics.com/ga.js
7200000 ms17 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
2558 ms
6 ms
2931 ms
15 ms
2983 ms
24 ms
JavaScript execution time - 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.

URL
Total CPU TimeScript EvaluationScript Parse
Other
167 ms12 ms3 ms
http://lendenmann.org/
86 ms83 ms1 ms
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.

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.

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

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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.

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

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) - v2

Suggestions Summary

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 780 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <p>Texte für Publ…en | Lyrisches</p> falls outside the viewport.
The element <a href="pages/texthumor2.html">chinesisch</a> falls outside the viewport.
The element <strong>Tor</strong> falls outside the viewport.
The element <p class="zehn"></p> falls outside the viewport.
The element <p class="zehn">PS. Nein, ich…che abzugeben.</p> falls outside the viewport.
The element <h1>Texte, die ankommen</h1> falls outside the viewport.
The element <p>Das Schreiben…se so ergeben.</p> falls outside the viewport.
The element <span class="p9oben">Psychologisches</span> falls outside the viewport.
The element <span class="p9oben">Bei Bedarf ges…enen Fotos an.</span> falls outside the viewport.
The element <a href="pages/texthumor.html">Kinderbücher</a> falls outside the viewport.
The element <p></p> falls outside the viewport.
The element <p></p> falls outside the viewport.
The element <form id="cse-search-box"></form> falls outside the viewport.
The element <p></p> falls outside the viewport.
The element <p>Textproben als PDFs  Sitemap &gt;</p> falls outside the viewport.
The element <a href="mailto:juerg@lendenmann.org">juerg@lendenmann.org</a> falls outside the viewport.
The element <a href="pages/sitemap.html" class="oben8weiss">Sitemap</a> falls outside the viewport.

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:

http://lendenmann.org/Library/jlxhtml.css

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://lendenmann.org/Library/jlxhtml.css (expiration not specified)
http://lendenmann.org/images/bu_pa_man_2015.png (expiration not specified)
https://cse.google.com/coop/cse/brand?form=cse-search-box&lang=de (30 minutes)
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 901B (60% reduction).

Compressing http://lendenmann.org/Library/jlxhtml.css could save 901B (60% reduction).
Optimize images
Your images are optimized. Learn more about optimizing images.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
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.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
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.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Download optimized image, JavaScript, and CSS resources for this page.

Does lendenmann.org use compression?

lendenmann.org does not use compression.
Original size: 5.55 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

lendenmann.org does not support HTTPS
loader
Verifying SSL Support. Please wait...

Verify HTTP/2 Support

lendenmann.org does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

Http Header

Content-Type: text/html
Last-Modified: Mon, 01 Jul 2019 13:19:28 GMT
Accept-Ranges: bytes
ETag: "e6bab29cf30d51:0"
Server: Microsoft-IIS/10.0
Date: Fri, 12 Jul 2019 13:04:04 GMT
Content-Length: 5680

DNS Lookup

Type Ip Target TTL
MX aspmx2.googlemail.com 3600
MX aspmx.l.google.com 3600
MX aspmx3.googlemail.com 3600
MX alt1.aspmx.l.google.com 3600
MX alt2.aspmx.l.google.com 3600
MX aspmx4.googlemail.com 3600
MX aspmx5.googlemail.com 3600
A 46.140.22.212 3600
SOA 3600
Mname hbackup
Rname nobody.invalid
Serial Number 2019011802
Refresh 10800
Retry 3600
Expire 777600
Minimum TTL 0
NS hbackup 3600

Whois Lookup

Domain Created:
2002-06-16
Domain Age:
17 years 26 days  
WhoIs:
 

whois lookup at whois.pir.org...
Domain Name: LENDENMANN.ORG
Registry Domain ID: D87587402-LROR
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.whois.godaddy.com
Updated Date: 2019-06-17T07:06:31Z
Creation Date: 2002-06-16T16:17:45Z
Registry Expiry Date: 2020-06-16T16:17:45Z
Registrar Registration Expiration Date:
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.4806242505
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: autoRenewPeriod https://icann.org/epp#autoRenewPeriod
Registrant Organization: hung.ch
Registrant State/Province:
Registrant Country: CH
Name Server: NS2.HITPARADE.CH
Name Server: NS2.HUNG.CH
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2019-07-12T13:03:32Z <<<

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

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 3 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

clubpenguin.com
6 secs
oryxyom.com
13 secs
normandiepass.com
13 secs
kingdomcultureproperties.com
15 secs
freeartnow.net
21 secs
aryfa.top
21 secs
clubplatinumx.com
21 secs
musclepulsegun.com
32 secs
irasaustralia.com.au
49 secs
lavsion.com
54 secs

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!
lendenmann.org widget