Your Website Score is

Similar Ranking

31
VFILMES
vfilmes.net
31
// KRNL.TO
krnl.to
31
TIKTOK DOWNLOADER - DOWNLOAD VIDEO TIKTOK WITHOUT WATERMARK - SNAPTIK
ssnaptik.app
31
PAISE KA FUNDA - LEARN TO EARN, SAVE & BUDGET
techinsights.live
31
DOOR HANDLE COMPANY | DOOR HANDLE & DOOR FURNITURE SPECIALISTS
doorhandlecompany.co.uk
31
CLUB BÀSQUET VILATORRADA BLOG - CLUB ESPORTIU AMATEUR DE BÀSQUET
cbvilatorrada.cat
31
RADIO TAXI NUMBERS IN CANADA | CAB DIRECTORY - RADIO TAXICAB
radio-taxi-cab.com

Latest Sites

19
WELCOME TO ISLAMICSTUDIES.INFO
islamicstudies.info
31
START - BIRGIT KLINNER
birgit-klinner.de
29
LAS ÚLTIMAS NOTICIAS DE ARGENTINA, ESPECTÁCULOS Y DEPORTES - MINUTOUNO
minutouno.com
31
MUKONDA EVENTOS | PLATAFORMA DE EVENTOS EM ANGOLA
mukondaeventos.com
91
INSTAGRAM
instagram.com
1
-
youtu.gmail.com
9
YOUTUBE
youtube.com

Top Technologies

Google Font API
Font Scripts
Nginx
Web Servers
jQuery
JavaScript Frameworks
CloudFlare
CDN
PHP
Programming Languages
Varnish
Cache Tools
Google Tag Manager
Tag Managers
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks
WordPress
CMS

31 birgit-klinner.de Last Updated: 3 hours

Success 78% of passed verification steps
Warning 7% of total warning
Errors 15% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 98%
Best Practices Desktop Score 78%
SEO Desktop Score 100%
Performance Mobile Score 82%
Best Practices Mobile Score 75%
SEO Mobile Score 100%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 22 Characters
START - BIRGIT KLINNER
Meta Description 132 Characters
Birgit Klinner. Praxis für Körpertherapie und Heilarbeit. Psychotherapie, Nachnähren (Bonding) und Workshops für Achtsame Berührung.
Effective URL 25 Characters
https://birgit-klinner.de
Excerpt Page content
Start - Birgit Klinner Tel 030 32 30 33 83 [email protected] Start Üb...
Keywords Cloud Density
berührung15 eine11 mehr10 deine9 achtsame9 sich9 lesen8 oder7 menschen7 geborgenheit6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
berührung 15
eine 11
mehr 10
deine 9
achtsame 9
sich 9
lesen 8
oder 7
menschen 7
geborgenheit 6
Google Preview Your look like this in google search result
START - BIRGIT KLINNER
https://birgit-klinner.de
Birgit Klinner. Praxis für Körpertherapie und Heilarbeit. Psychotherapie, Nachnähren (Bonding) und Workshops für Achtsame Berührung.
Robots.txt File Detected
http://birgit-klinner.de/robots.txt
Sitemap.xml File Detected
http://birgit-klinner.de/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~193.55 KB
Code Size: ~27.28 KB
Text Size: ~166.27 KB Ratio: 85.91%

Social Data

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Improve image delivery Est savings of 404 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
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
Use efficient cache lifetimes Est savings of 676 KiB
A long cache lifetime can speed up repeat visits to your page
Does not use HTTPS 1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Avoids an excessive DOM size 235 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)
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
Serve static assets with an efficient cache policy 23 resources found
A long cache lifetime can speed up repeat visits to your page
Serve images in next-gen formats Est savings of 410 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
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
Max Potential First Input Delay 30 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Initial server response time was short Root document took 110 ms
Keep the server response time for the main document short because all other requests depend on it
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids enormous network payloads Total size was 710 KiB
Large network payloads cost users real money and are highly correlated with long load times
Efficiently encode images Est savings of 13 KiB
Optimized images load faster and consume less cellular data
Server Backend Latencies 100 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
Avoid serving legacy JavaScript to modern browsers Est savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Font display Est savings of 540 ms
Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
Reduce unused CSS Est savings of 18 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Largest Contentful Paint element 580 ms
This is the largest contentful element painted within the viewport
Avoid large layout shifts 4 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Time to Interactive 0.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted
Cumulative Layout Shift 0.089
Cumulative Layout Shift measures the movement of visible elements within the viewport
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Properly size images Est savings of 55 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Reduce unused JavaScript Est savings of 75 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid chaining critical requests 13 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
Legacy JavaScript Est savings of 8 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Largest Contentful Paint 0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted

Mobile

Mobile Screenshot
Initial server response time was short Root document took 220 ms
Keep the server response time for the main document short because all other requests depend on it
Improve image delivery Est savings of 414 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Largest Contentful Paint element 3,490 ms
This is the largest contentful element painted within the viewport
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
Serve images in next-gen formats Est savings of 393 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid chaining critical requests 13 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
Legacy JavaScript Est savings of 8 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Cumulative Layout Shift 0.201
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Avoid serving legacy JavaScript to modern browsers Est savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Use efficient cache lifetimes Est savings of 654 KiB
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 3.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Font display Est savings of 310 ms
Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
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
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint 3.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid large layout shifts 4 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Properly size images Est savings of 27 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Avoids an excessive DOM size 233 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)
Avoids enormous network payloads Total size was 688 KiB
Large network payloads cost users real money and are highly correlated with long load times
Reduce unused JavaScript Est savings of 75 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Serve static assets with an efficient cache policy 22 resources found
A long cache lifetime can speed up repeat visits to your page
Does not use HTTPS 1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Reduce unused CSS Est savings of 18 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Congratulations! Your site not have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links
First 16 Links Relationship HTTP Status
https://birgit-klinner.de/ Internal Link 200
Über mich Internal Link 200
Körper Internal Link 200
Seele Internal Link 200
Workshops Internal Link 200
English Internal Link 200
Kontakt und Impressum Internal Link 200
FrauenHeilKreis Internal Link 200
Trauma und Armut Internal Link 200
Wie läuft eine Kuschelparty ab? Internal Link 200
Frauenkuscheln Internal Link 200
Kuschelparty? Ist nichts für mich Internal Link 200
Nachnähren – wie geht das? Internal Link 200
Jeder ist der Richtige? Internal Link 200
Berührungsqualität – Kann man gute Berührung lernen? Internal Link 200
Datenschutz Internal Link 200

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
birgit-klinner.co Available
birgit-klinner.us Available
birgit-klinner.com Available
birgit-klinner.org Available
birgit-klinner.net Available
brgit-klinner.de Available
girgit-klinner.de Available
yirgit-klinner.de Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/1.1 200 OK
Server: nginx
Date: Sat, 13 Sep 2025 17:55:36 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Link: ; rel="https://api.w.org/", ; rel="alternate"; title="JSON"; type="application/json", ; rel=shortlink
X-Cache-Status: HIT
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A birgit-klinner.de 92.205.49.113 IN 3522
NS birgit-klinner.de ns01.domaincontrol.com IN 3600
NS birgit-klinner.de ns02.domaincontrol.com IN 3600
MX birgit-klinner.de mxlb.ispgateway.de IN 3600
TXT birgit-klinner.de v=spf1 mx include:ispgateway.de -all IN 3600
AAAA birgit-klinner.de 2a00:1169:103:8460:: IN 3523

About Us

We provide SEO metrics for your website. There are many who have trusted on us and improved their position thanks to our recommendations

Contact Info

RYIN
10407 Feeney Trafficway Apt. 577
Maryland Line
1-760-992-3170
[email protected]

Follow Us

Facebook
© Copyright 2023
Languages | English