Your Website Score is

Similar Ranking

6
HOME : WWW.FOOTBALLFORUM.DE - DAS FORUM FÜR AMERICAN FOOTBALL IN DEUTSCHLAND
footballforum.de
6
THE PAGE IS TEMPORARILY UNAVAILABLE
beach.de
6
THE PAGE IS TEMPORARILY UNAVAILABLE
papp-paletten.com
6
THE PAGE IS TEMPORARILY UNAVAILABLE
automaxx.de
6
THE PAGE IS TEMPORARILY UNAVAILABLE
4amtechno.com
6
NEUE DOMAIN BEI DER WEBGO GMBH
resteplatz.com
6
RSS NEWS VERZEICHNIS
indexking.de

Latest Sites

43
A HOUSE IN THE HILLS - DESIGNING SPACES FOR LIVING
ahouseinthehills.com
29
GRIECHISCHE MYTHOLOGIE UND ANTIKE (KOMBINATION)
mythologie-antike.com
51
RICHMONDMOM - NAVIGATING PARENTHOOD, TOGETHER
richmondmom.com
50
FNF4 - FIVENIGHTSATFREDDYS-4.COM
fivenightsatfreddys-4.com
48
BT - TRAVEL NEWS & INFORMATION
besttravelever.my.id
49
VIH - INFORMATION ABOUT TRAVEL WORLD NEWS
veniceitalyhotels.org
31
MAXCIOMENU - BUSCADOR DE MENÚS EN TODO MÉXICO
maxciomenu.xyz

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

6 footballforum.de Last Updated: 3 weeks

Success 40% of passed verification steps
Warning 30% of total warning
Errors 30% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 88%
Best Practices Desktop Score 96%
SEO Desktop Score 92%
Performance Mobile Score 66%
Best Practices Mobile Score 89%
SEO Mobile Score 92%
Page Authority Authority 35%
Domain Authority Domain Authority 22%
Moz Rank 3.5/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 86 Characters
HOME : WWW.FOOTBALLFORUM.DE - DAS FORUM FÜR AMERICAN FOOTBALL IN DEUTSCHLAND
Meta Description 105 Characters
Herzlich Willkommen bei footballforum.de, der Diskussionsplattform über American Football in Deutschland.
Effective URL 38 Characters
https://www.footballforum.de/home.html
Excerpt Page content
Home : www.footballforum.de - Das Forum für American Football in Deutschland Toggle navigation ...
Keywords Cloud Density
erstellt28 weiterlesen28 football24 league20 german20 razorbacks13 phantoms12 gegen12 wiesbaden11 assindia10
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
erstellt 28
weiterlesen 28
football 24
league 20
german 20
razorbacks 13
phantoms 12
gegen 12
wiesbaden 11
assindia 10
Google Preview Your look like this in google search result
HOME : WWW.FOOTBALLFORUM.DE - DAS FORUM FÜR AMERIC
https://www.footballforum.de/home---
Herzlich Willkommen bei footballforum.de, der Diskussionsplattform über American Football in Deutschland.
Robots.txt File No Found
http://footballforum.de/robots.txt
Sitemap.xml File No Found
http://footballforum.de/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~53.95 KB
Code Size: ~44.3 KB
Text Size: ~9.64 KB Ratio: 17.88%

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
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
Avoids enormous network payloads Total size was 637 KiB
Large network payloads cost users real money and are highly correlated with long load times
Font display Est savings of 10 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).
Eliminate render-blocking resources Est savings of 280 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Time to Interactive 1.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
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
Largest Contentful Paint 1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce unused JavaScript Est savings of 245 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Legacy JavaScript Est savings of 9 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
Minimize third-party usage Third-party code blocked the main thread for 10 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
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid an excessive DOM size 5,602 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)
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
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minify CSS Est savings of 4 KiB
Minifying CSS files can reduce network payload sizes
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
Improve image delivery Est savings of 28 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Speed Index 3.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid large layout shifts 3 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.003
Cumulative Layout Shift measures the movement of visible elements within the viewport
Render blocking requests Est savings of 340 ms
Requests are blocking the page's initial render, which may delay LCP
Network Round Trip Times 10 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
Document request latency Est savings of 2,370 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Minify JavaScript Est savings of 40 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Serve images in next-gen formats Est savings of 39 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 1,340 ms
This is the largest contentful element painted within the viewport
Initial server response time was short Root document took 360 ms
Keep the server response time for the main document short because all other requests depend on it
Links do not have descriptive text 170 links found
Descriptive link text helps search engines understand your content
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
Reduce unused CSS Est savings of 31 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Serve static assets with an efficient cache policy 10 resources found
A long cache lifetime can speed up repeat visits to your page

Mobile

Mobile Screenshot
Initial server response time was short Root document took 30 ms
Keep the server response time for the main document short because all other requests depend on it
Minify JavaScript Est savings of 40 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Render blocking requests Est savings of 1,400 ms
Requests are blocking the page's initial render, which may delay LCP
Total Blocking Time 150 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce unused CSS Est savings of 32 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Defer offscreen images Est savings of 20 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Serve images in next-gen formats Est savings of 23 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid an excessive DOM size 5,674 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)
Document doesn't use legible font sizes 44.15% 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
Eliminate render-blocking resources Est savings of 1,130 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Links do not have descriptive text 170 links found
Descriptive link text helps search engines understand your content
Legacy JavaScript Est savings of 9 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
Serve static assets with an efficient cache policy 8 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element 6,040 ms
This is the largest contentful element painted within the viewport
Avoids enormous network payloads Total size was 615 KiB
Large network payloads cost users real money and are highly correlated with long load times
Network Round Trip Times 10 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
Time to Interactive 6.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Max Potential First Input Delay 130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minimizes main-thread work 0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 8.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid long main-thread tasks 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
JavaScript execution time 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint 6.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce unused JavaScript Est savings of 222 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
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
Minimize third-party usage Third-party code blocked the main thread for 190 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
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
Minify CSS Est savings of 4 KiB
Minifying CSS files can reduce network payload sizes
First Contentful Paint 2.1 s
First Contentful Paint marks the time at which the first text or image is painted
Document request latency Est savings of 2,050 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Improve image delivery Est savings of 24 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP

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
Warning! Your title is not optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
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
http://footballforum.de/index--- Internal Link 301
GFL Internal Link 301
Spielplan Internal Link 301
GFL 2 Internal Link 301
Spielpläne der 2. Bundesliga im American Football Internal Link 301
GFL Juniors Internal Link 301
Spielplan Internal Link 301
DFFL Internal Link 301
Damenfootball Internal Link 301
Spielplan Internal Link 301
Regionalliga Internal Link 301
Spielplan Internal Link 301
Oberliga Internal Link 301
EFAF, Eurobowl Internal Link 301
Impressum Internal Link 301
Copyright Internal Link 301
Datenschutzerklärung Internal Link 301
Kontakt Internal Link 301
Forum Internal Link 301
Wichtiges Auswärtsspiel im Saarland Internal Link 301

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/1.1 200 OK
Date: Sat, 25 Oct 2025 13:12:28 GMT
Server: Apache/2.4.37 (Rocky Linux) OpenSSL/1.1.1k SVN/1.10.2
X-Powered-By: PHP/7.3.33
Content-Language: de
Expires: Sat, 25 Oct 2025 13:30:06 GMT
Cache-Control: max-age=1058
Pragma: public
Content-Encoding: gzip
Vary: Accept-Encoding,User-Agent
Strict-Transport-Security: max-age=15768000; includeSubDomains; preload
X-UA-Compatible: IE=edge
X-Content-Type-Options: nosniff
Content-Type: text/html; charset=utf-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A footballforum.de 85.214.138.131 IN 59
NS footballforum.de nsb9.schlundtech.de IN 86400
NS footballforum.de ns.footballforum.de IN 86400
MX footballforum.de mail.footballforum.de IN 86400
TXT footballforum.de v=spf1 a mx IN 86400
TXT footballforum.de google-site-verification=OPXP9XRGJnijSBo2L-7LQjTJYBqtuahY5iEtJmYmDm0 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