Your Website Score is

Similar Ranking

41
HOME - OPEN-REPORT.DE
open-report.de
41
DAS ELEKTROAUTO FORUM - ALLES ZUM THEMA ELEKTROMOBILITÄT ?
elektroauto-forum.de
41
HOME - TECH VIRTUAL
thetechvirtual.com
41
GRIECHISCHE MYTHOLOGIE IN KOMBINATION MIT ANTIKE
mythologie-antike.com
41
STERBEKASSE HARDT MÖNCHENGLADBACH
hp-mg.de
41
INETSU - DEINE ALLROUND-SUCHMASCHINE
inetsu.com
41
MEER SEO
meerseo.com

Latest Sites

21
STEADY CLIMBING GMBH – INDUSTRIEKLETTERER – DIE GÜNSTIGE & SICHERE ALTERNATIVE
steady-climbing.de
26
DETLEF FUNDER ART
parallelworld.eu
92
GOOGLE
google.com
3
CAFFIA SHOP
shop.caffia.de
18
KAFFEEVOLLAUTOMATEN MIETEN, LEASEN ODER KAUFEN | CAFFIA LEIPZIG
caffia.de
33
SABONA OF LONDON SCHWEIZ EXKLUSIVER KUPFER- & MAGNETSCHMUCK
sabona-ch.com
23
503 SERVICE TEMPORARILY UNAVAILABLE
katzenfreunde-online.de

Top Technologies

Apache
Web Servers
WordPress
CMS
Google Font API
Font Scripts
Nginx
Web Servers
Font Awesome
Font Scripts
Yoast SEO
SEO
Google AdSense
Advertising Networks
CloudFlare
CDN

41 elektroauto-forum.de Last Updated: 3 weeks

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

Desktop

Mobile

Performance Desktop Score 90%
Best Practices Desktop Score 78%
SEO Desktop Score 92%
Performance Mobile Score 56%
Best Practices Mobile Score 75%
SEO Mobile Score 92%
Page Authority Authority 39%
Domain Authority Domain Authority 31%
Moz Rank 3.9/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 58 Characters
DAS ELEKTROAUTO FORUM - ALLES ZUM THEMA ELEKTROMOBILITÄT ?
Meta Description 110 Characters
Wir sind deine E-Mobility Community - Das Forum für technische Probleme, Batterien und Fragen zum Elektroauto.
Effective URL 28 Characters
https://elektroauto-forum.de
Excerpt Page content
Das Elektroauto Forum - Alles zum Thema Elektromobilität ? Suche Nur Titel durchsuchen Von: Suche Erweiterte Suche... Nur Titel durchsuchen Von: ...
Keywords Cloud Density
unterforen56 beiträge51 themen49 elektroautos34 forum30 alles27 elektroauto27 suche11 smart9 renault9
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
unterforen 56
beiträge 51
themen 49
elektroautos 34
forum 30
alles 27
elektroauto 27
suche 11
smart 9
renault 9
Google Preview Your look like this in google search result
DAS ELEKTROAUTO FORUM - ALLES ZUM THEMA ELEKTROMOBILITÄT ?
https://elektroauto-forum.de
Wir sind deine E-Mobility Community - Das Forum für technische Probleme, Batterien und Fragen zum Elektroauto.
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~179.62 KB
Code Size: ~146.39 KB
Text Size: ~33.22 KB Ratio: 18.50%

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

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Server Backend Latencies 20 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
Serve static assets with an efficient cache policy 37 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint 1.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Use efficient cache lifetimes Est savings of 1,618 KiB
A long cache lifetime can speed up repeat visits to your page
Avoid large layout shifts 1 layout shift 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)
Largest Contentful Paint element 1,820 ms
This is the largest contentful element painted within the viewport
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Reduce unused JavaScript Est savings of 404 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Speed Index 1.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoids enormous network payloads Total size was 2,162 KiB
Large network payloads cost users real money and are highly correlated with long load times
Time to Interactive 1.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Enable text compression Est savings of 397 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Improve image delivery Est savings of 149 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Minimizes main-thread work 0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
JavaScript execution time 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 57 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
Reduce unused CSS Est savings of 215 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 12 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
Initial server response time was short Root document took 120 ms
Keep the server response time for the main document short because all other requests depend on it
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
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimize third-party usage Third-party code blocked the main thread for 40 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 an excessive DOM size 2,800 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)
Properly size images Est savings of 121 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Serve images in next-gen formats Est savings of 92 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Efficiently encode images Est savings of 6 KiB
Optimized images load faster and consume less cellular data
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Eliminate render-blocking resources Est savings of 790 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted
Total Blocking Time 40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

Mobile

Mobile Screenshot
Avoid chaining critical requests 12 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
Largest Contentful Paint 14.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Total Blocking Time 130 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Largest Contentful Paint element 14,120 ms
This is the largest contentful element painted within the viewport
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Enable text compression Est savings of 397 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Use efficient cache lifetimes Est savings of 1,625 KiB
A long cache lifetime can speed up repeat visits to your page
Improve image delivery Est savings of 142 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Reduce unused CSS Est savings of 216 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Reduce unused JavaScript Est savings of 396 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Time to Interactive 14.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Efficiently encode images Est savings of 6 KiB
Optimized images load faster and consume less cellular data
Avoid serving legacy JavaScript to modern browsers Est savings of 57 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
Serve static assets with an efficient cache policy 23 resources found
A long cache lifetime can speed up repeat visits to your page
Defer offscreen images Est savings of 71 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Cumulative Layout Shift 0.006
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoids enormous network payloads Total size was 2,170 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid large layout shifts 1 layout shift 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 120 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Max Potential First Input Delay 150 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Document uses legible font sizes 95.26% 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
First Contentful Paint 6.5 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index 7.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Minimize third-party usage Third-party code blocked the main thread for 100 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 60 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 an excessive DOM size 2,800 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)
Minimizes main-thread work 1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Initial server response time was short Root document took 190 ms
Keep the server response time for the main document short because all other requests depend on it
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
Serve images in next-gen formats Est savings of 115 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Eliminate render-blocking resources Est savings of 4,440 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

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
Congratulations! Your Domain Authority is good
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

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 
x-content-type-options: nosniff
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: private, no-cache, max-age=0
content-encoding: gzip
vary: Accept-Encoding
set-cookie: xf_csrf=K4NDnq5Z0kfg7dwi; path=/; secure
last-modified: Sun, 04 May 2025 12:12:15 GMT
content-length: 34069
content-type: text/html; charset=utf-8
date: Sun, 04 May 2025 12:12:15 GMT
server: Apache
DNS Records DNS Resource Records associated with a hostname
View DNS Records