Your Website Score is

Similar Ranking

19
TAXI IN TÜBINGEN UND UMGEBUNG - WWW.TAXISTA.DE
taxista.de
19
BLIMEY SOLUTIONS LTD - CIS ACCOUNTING & RECRUITMENT SERVICES IN LONDON
blimeysolutions.com
19
FUNKHORST.DE - IHR SPEZIALIST FÜR FUNKGERÄTE UND FUNKTECHNIK
funkhorst.de
19
EROTIK DELUXE - DAS EROTISCHE DATING-PORTAL
erotikdeluxe.de
19
WETTERSTATION LISTERFEHRDA
wetter-listerfehrda.de
19
GOOUTBECRAZY - DER FAMILIEN REISEBLOG
gooutbecrazy.com
19
ELEKTRO SCOOTER KAUFEN | HOCHWERTIGE E SCOOTER VON SXT
e-wheels.ch

Latest Sites

6
THE PAGE IS TEMPORARILY UNAVAILABLE
automaxx.de
12
THE PAGE IS TEMPORARILY UNAVAILABLE
promiplanet.de
36
-
allnews24.eu
29
REICHELT ELECTRIC
norei.de
13
CLUB AND INTERNATIONAL FOOTBALL COEFFICIENTS AND RANKINGS - FOOTBALLSEEDING.COM
footballseeding.com
34
MONSTERZEUG - SCHENKEN MACHT GLÜCKLICH
monsterzeug.de
28
DAS SURFCAMP VERZEICHNIS - 600 SURFCAMPS ÜBERSICHTLICH SORTIERT!
surfcamp-online.com

Top Technologies

PHP
Programming Languages
Apache
Web Servers
WordPress
CMS
Google Font API
Font Scripts
jQuery
JavaScript Frameworks
Nginx
Web Servers
Font Awesome
Font Scripts
Yoast SEO
SEO
Google AdSense
Advertising Networks
CloudFlare
CDN

19 teeguru.net Last Updated: 5 days

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

Desktop

Mobile

Performance Desktop Score 58%
Best Practices Desktop Score 93%
SEO Desktop Score 100%
Performance Mobile Score 48%
Best Practices Mobile Score 93%
SEO Mobile Score 100%
Page Authority Authority 1%
Domain Authority Domain Authority 1%
Moz Rank 0.1/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 20 Characters
STARTSEITE - TEEGURU
Meta Description 78 Characters
Alles um das Getränk der Götter - unabhängig, leidenschaftlich und authentisch
Effective URL 19 Characters
https://teeguru.net
Excerpt Page content
Startseite - Teeguru Zum Inhalt springen ...
Keywords Cloud Density
teeguru17 über8 neuen7 welt5 seine5 immer4 tees4 eine4 teeleidenschaft3 alles3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
teeguru 17
über 8
neuen 7
welt 5
seine 5
immer 4
tees 4
eine 4
teeleidenschaft 3
alles 3
Google Preview Your look like this in google search result
STARTSEITE - TEEGURU
https://teeguru.net
Alles um das Getränk der Götter - unabhängig, leidenschaftlich und authentisch
Robots.txt File Detected
http://teeguru.net/robots.txt
Sitemap.xml File Detected
http://teeguru.net/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~224.51 KB
Code Size: ~78.53 KB
Text Size: ~145.97 KB Ratio: 65.02%

Estimation Traffic and Earnings

0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Serve static assets with an efficient cache policy 6 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids an excessive DOM size 558 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)
Enable text compression Potential savings of 93 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Speed Index 2.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint element 2,350 ms
This is the largest contentful element painted within the viewport
Total Blocking Time 570 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Server Backend Latencies 220 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
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Properly size images Potential savings of 183 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid large layout shifts 2 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)
Cumulative Layout Shift 0.018
Cumulative Layout Shift measures the movement of visible elements within the viewport
Initial server response time was short Root document took 250 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids enormous network payloads Total size was 2,483 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid non-composited animations 7 animated elements found
Animations which are not composited can be janky and increase CLS
Time to Interactive 2.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Reduce unused CSS Potential savings of 52 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Serve images in next-gen formats Potential savings of 436 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Minimizes main-thread work 1.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Reduce the impact of third-party code Third-party code blocked the main thread for 620 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
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
JavaScript execution time 1.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint 2.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Max Potential First Input Delay 590 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Reduce unused JavaScript Potential savings of 296 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Eliminate render-blocking resources Potential savings of 370 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid chaining critical requests 57 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
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

Mobile

Mobile Screenshot
Reduce the impact of third-party code Third-party code blocked the main thread for 680 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
Avoids an excessive DOM size 558 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)
Serve images in next-gen formats Potential savings of 415 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Largest Contentful Paint element 13,060 ms
This is the largest contentful element painted within the viewport
Total Blocking Time 660 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Document uses legible font sizes 99.75% 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
Reduce unused CSS Potential savings of 52 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid chaining critical requests 58 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
Minimizes main-thread work 1.9 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 570 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Reduce unused JavaScript Potential savings of 296 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Eliminate render-blocking resources Potential savings of 1,720 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoids enormous network payloads Total size was 2,446 KiB
Large network payloads cost users real money and are highly correlated with long load times
Time to Interactive 13.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Serve static assets with an efficient cache policy 6 resources found
A long cache lifetime can speed up repeat visits to your page
Speed Index 6.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Enable text compression Potential savings of 93 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Initial server response time was short Root document took 210 ms
Keep the server response time for the main document short because all other requests depend on it
JavaScript execution time 1.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid non-composited animations 7 animated elements found
Animations which are not composited can be janky and increase CLS
Properly size images Potential savings of 118 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
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
First Contentful Paint 2.9 s
First Contentful Paint marks the time at which the first text or image is painted
Server Backend Latencies 160 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 long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint 13.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted

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
Warning! Your site 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 20 Links Relationship HTTP Status
https://teeguru.net Internal Link 200
Teenews Internal Link 200
Tee-Weltreise Internal Link 200
Teeliteratur Internal Link 200
Teesorten Internal Link 200
schwarzer Tee Internal Link 200
Pu Erh Tee Internal Link 200
grüner Tee Internal Link 200
gelber Tee Internal Link 200
Matchatee Internal Link 200
Kombucha Internal Link 200
Früchtetee Internal Link 200
roter Tee Internal Link 200
Kräutertee Internal Link 200
Pfefferminztee Internal Link 200
Kamillentee Internal Link 200
Salbeitee Internal Link 200
Moringatee Internal Link 200
Beifusstee Internal Link 200
Oolongtee Internal Link 200

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/2 200 
server: nginx
date: Sat, 11 Jan 2025 11:48:30 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
link: ; rel="https://api.w.org/", ; rel="alternate"; title="JSON"; type="application/json", ; rel=shortlink
x-tec-api-version: v1
x-tec-api-root: https://teeguru.net/wp-json/tribe/events/v1/
x-tec-api-origin: https://teeguru.net
x-httpd: 1
host-header: 8441280b0c35cbc1147f8ba998a563a7
x-proxy-cache-info: DT:1
content-encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A teeguru.net 35.208.69.149 IN 86305
NS teeguru.net ns1.siteground.net IN 86400
NS teeguru.net ns2.siteground.net IN 86400
MX teeguru.net mx20.antispam.mailspamprotection.com IN 86400
MX teeguru.net mx30.antispam.mailspamprotection.com IN 86400
MX teeguru.net mx10.antispam.mailspamprotection.com IN 86400
TXT teeguru.net v=spf1 +a +mx +ip4:35.208.1.62 include:teeguru.net.spf.auto.dnssmarthost.net ~all IN 14400
TXT teeguru.net google-site-verification=G7MyFNG5Im36rlSVwhEzEMVtBlq4kdyeER2Vc7tQ-8g IN 86400

About Us

Contact Info

Follow Us

Copyright 2021 - 2023 Webseitenwert.de - Alle Rechte vorbehalten | Impressum | Datenschutz | Imprint | Data Protection | Cookie-Einstellungen
Languages | English