Your Website Score is

Similar Ranking

29
PETRAS KOCHBUCH – KOCHEN, STRICKEN UND SPASS
pewro.de
29
❶ SEO ---YSIS TOOL • FREE WEBSITE TOOLS • RANK BOOSTER[NEW!]
directorylib.com
29
❶ SEO ---YSIS TOOL • FREE WEBSITE TOOLS • RANK BOOSTER[NEW!]
stiripesurse.directorylib.com
29
BLUMIGO
blumigo.de
29
REICHELT ELECTRIC
norei.de
29
DAS ELEKTROAUTO FORUM - ALLES ZUM THEMA ELEKTROMOBILITÄT ?
elektroauto-forum.de
28
DEIN VERANSTALTUNGSPORTAL FÜR DIE GANZE WELT - MIT GÜNSTIGEN ONLINE-TICKETS | PERTO.COM
perto.com

Latest Sites

26
TECHONTRENDZ
techontrendz.wordpress.com
18
STARTSEITE | ONMYLIST.DE
onmylist.de
23
UNSER BAUBLOG - UNSER HAUSBAU MIT DER BAU-GMBH ROTH IM ROUSSEAU PARK IN LUDWIGSFELDE.
unserbaublog.de
34
BOS-FAHRZEUGE - EINSATZFAHRZEUGE UND WACHEN WELTWEIT
bos-fahrzeuge.info
3
THE PAGE IS TEMPORARILY UNAVAILABLE
gimp-handbuch.de
85
HERZLICH WILLKOMMEN – MUSIKHAUS THOMANN
thomann.de
9
POLOLOGO.DE - NEWS MAL ANDERS... - NACHRICHTEN, UNTERHALTUNG UND MEHR...
polologo.de

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

29 elektroauto-forum.de Last Updated: 4 weeks

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 93%
Best Practices Desktop Score 92%
SEO Desktop Score 92%
PWA Desktop Score 33%
Performance Mobile Score 56%
Best Practices Mobile Score 83%
SEO Mobile Score 89%
PWA Mobile Score 40%
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
beiträge36 themen33 unterforen17 forum13 suche10 gestern8 category8 elektrofahrzeuge7 durchsuchen6 laden6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
beiträge 36
themen 33
unterforen 17
forum 13
suche 10
gestern 8
category 8
elektrofahrzeuge 7
durchsuchen 6
laden 6
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
http://elektroauto-forum.de/robots.txt
Sitemap.xml File Detected
http://elektroauto-forum.de/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~128.94 KB
Code Size: ~104.75 KB
Text Size: ~24.19 KB Ratio: 18.76%

Estimation Traffic and Earnings

111
Unique Visits
Daily
205
Pages Views
Daily
$0
Income
Daily
3,108
Unique Visits
Monthly
5,843
Pages Views
Monthly
$0
Income
Monthly
35,964
Unique Visits
Yearly
68,880
Pages Views
Yearly
$0
Income
Yearly

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

Login

PWA - Manifest

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

Desktop

Desktop Screenshot
Eliminate render-blocking resources Potential savings of 440 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 1,317 KiB
Large network payloads cost users real money and are highly correlated with long load times
Initial server response time was short Root document took 200 ms
Keep the server response time for the main document short because all other requests depend on it
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Serve images in next-gen formats Potential 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
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
Largest Contentful Paint 1.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoid an excessive DOM size 1,911 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 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid chaining critical requests 11 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
Reduce unused CSS Potential savings of 94 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible
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
Minimize third-party usage Third-party code blocked the main thread for 0 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
Keep request counts low and transfer sizes small 38 requests • 1,317 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Efficiently encode images Potential savings of 10 KiB
Optimized images load faster and consume less cellular data
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Cumulative Layout Shift 0.006
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce unused JavaScript Potential savings of 72 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Time to Interactive 1.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
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 28 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
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

Mobile

Mobile Screenshot
Time to Interactive 8.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Reduce unused JavaScript Potential savings of 72 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid large layout shifts 1 element found
These DOM elements contribute most to the CLS of the page.
Serve static assets with an efficient cache policy 19 resources found
A long cache lifetime can speed up repeat visits to your page
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
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
Tap targets are not sized appropriately 53% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Initial server response time was short Root document took 140 ms
Keep the server response time for the main document short because all other requests depend on it
Total Blocking Time 70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
JavaScript execution time 0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid an excessive DOM size 1,911 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)
First Contentful Paint 5.0 s
First Contentful Paint marks the time at which the first text or image is painted
Avoids enormous network payloads Total size was 1,327 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Keep request counts low and transfer sizes small 28 requests • 1,327 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Reduce unused CSS Potential savings of 95 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
First Contentful Paint (3G) 10853 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Document uses legible font sizes 99.6% 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
Efficiently encode images Potential savings of 6 KiB
Optimized images load faster and consume less cellular data
Minimizes main-thread work 1.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Meaningful Paint 5.0 s
First Meaningful Paint measures when the primary content of a page is visible
Eliminate render-blocking resources Potential savings of 4,010 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 150 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint 8.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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 images in next-gen formats Potential savings of 62 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid long main-thread tasks 9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Speed Index 5.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Defer offscreen images Potential savings of 55 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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 chaining critical requests 11 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

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
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
First 20 Links Relationship HTTP Status
https://elektroauto-forum.de Internal Link 200
Suche Internal Link 301
News Internal Link 301
Neuigkeiten Internal Link 301
Letzten Aktivitäten Internal Link 301
Redaktionsteam Internal Link 200
Foren Internal Link 301
Neue Beiträge Internal Link 301
Foren durchsuchen Internal Link 301
Kalender Internal Link 301
Kleinanzeigen Internal Link 301
Neue Kleinanzeigen Internal Link 301
Seiten Internal Link 200
Übersicht Internal Link 301
Letzten Änderungen Internal Link 301
Anmelden Internal Link 301
Registrieren Internal Link 301
articles Internal Link 301
Willkommen Internal Link 301
I Internal Link 301

Alexa Rank

0

Local Rank: / Users: / PageViews:

2,897,536

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
Server: nginx
Date: Fri, 04 Nov 2022 07:12:04 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 26270
Connection: keep-alive
X-Powered-By: PHP/7.4.32
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=IRKQVfaom5SQ_L7m; path=/; secure
Last-Modified: Fri, 04 Nov 2022 07:12:04 GMT
X-Powered-By: PleskLin
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A elektroauto-forum.de 212.227.73.54 IN 86347
NS elektroauto-forum.de ns.nameway.eu IN 86400
NS elektroauto-forum.de ns.nameway.ch IN 86400
NS elektroauto-forum.de ns.nameway.at IN 86400
NS elektroauto-forum.de ns.nameway.de IN 86400
MX elektroauto-forum.de redirect.domain-robot.org IN 86400
TXT elektroauto-forum.de v=spf1 +a +mx include:spf-redirector.domain-robot.org ~all IN 86400
TXT elektroauto-forum.de google-site-verification=3-G-RvWvch9KxqrLD3tzmR3kHZYgV8TdSZF1S7EUQB0 IN 86400

About Us

Contact Info

Follow Us

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