Your Website Score is

Similar Ranking

19
BERG-VAN:MAG - INFOS ZU BERGTOUREN UND WANDERN MIT HUND - TIPPS UND ERFAHRUNGEN ZU BERGTOUREN UND WANDERUNGEN (MIT HUND) PLUS TESTS VON EQUIPMENT UND AUSRÜSTUNG
berg-van.com
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
FAMILIEN REISEBLOG - GOOUTBECRAZY
gooutbecrazy.com

Latest Sites

31
SOTECON • IT-SYSTEMHAUS
sotecon.de
19
WETTERSTATION LISTERFEHRDA
wetter-listerfehrda.de
31
ITINSIGHTNEWS.COM
itinsightnews.com
28
EDELMETALLANKAUF SEIT MEHR ALS 25 JAHREN | GOLDANKAUF-BOERSE.DE
goldankauf-boerse.de
32
GOLD, SILBER & EDELMETALLE SICHER ONLINE KAUFEN UND VERKAUFEN
goldsilbershop.de
28
GOLDANKAUF – ONLINE GOLD VERKAUFEN ZU HOHEN PREISEN
moneygold.de
31
RENT PREMIUM FURNITURE & HOME APPLIANCES ONLINE - CITYFURNISH
cityfurnish.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 e-wheels.ch Last Updated: 2 weeks

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

Desktop

Mobile

Performance Desktop Score 45%
Best Practices Desktop Score 100%
SEO Desktop Score 85%
Performance Mobile Score 16%
Best Practices Mobile Score 96%
SEO Mobile Score 85%
Page Authority Authority 29%
Domain Authority Domain Authority 20%
Moz Rank 2.9/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 60 Characters
E-SCOOTER | VIELFäLTIGE AUSWAHL – TOP-QUALITäT | E-WHEELS.CH
Meta Description 170 Characters
Erleben Sie umweltfreundliche Premium-E-Scooter von E-Wheels in der Schweiz. Genießen Sie höchste Qualität, Sicherheit und Fahrspaß – jetzt bestellen!
Effective URL 38 Characters
https://www.ewheels.ch/de-ch/e-scooter
Excerpt Page content
E-Scooter | Vielfältige Auswahl – Top-Qualität | E-Wheels.ch ...
Keywords Cloud Density
wheels24 scooter17 oder9 unsere8 eine8 produkte6 ersatzteile6 schweiz6 bieten6 kundenservice5
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
wheels 24
scooter 17
oder 9
unsere 8
eine 8
produkte 6
ersatzteile 6
schweiz 6
bieten 6
kundenservice 5
Google Preview Your look like this in google search result
E-SCOOTER | VIELFäLTIGE AUSWAHL – TOP-QUALITäT | E-WHEELS.CH
https://www.ewheels.ch/de-ch/e-scooter
Erleben Sie umweltfreundliche Premium-E-Scooter von E-Wheels in der Schweiz. Genießen Sie höchste Qualität, Sicherheit und Fahrspaß
Robots.txt File Detected
http://e-wheels.ch/robots.txt
Sitemap.xml File Detected
http://e-wheels.ch/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~246.46 KB
Code Size: ~61.67 KB
Text Size: ~184.78 KB Ratio: 74.98%

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
Preload Largest Contentful Paint image Potential savings of 220 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP
Serve images in next-gen formats Potential savings of 349 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Max Potential First Input Delay 430 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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)
Reduce JavaScript execution time 2.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoids enormous network payloads Total size was 2,088 KiB
Large network payloads cost users real money and are highly correlated with long load times
Total Blocking Time 850 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve static assets with an efficient cache policy 21 resources found
A long cache lifetime can speed up repeat visits to your page
Defer offscreen images Potential savings of 4 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 471 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Network Round Trip Times 30 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
Minimize main-thread work 4.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint 3.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce unused JavaScript Potential savings of 589 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid an excessive DOM size 2,541 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 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
Initial server response time was short Root document took 540 ms
Keep the server response time for the main document short because all other requests depend on it
Efficiently encode images Potential savings of 229 KiB
Optimized images load faster and consume less cellular data
Server Backend Latencies 410 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
Reduce unused CSS Potential savings of 97 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 1.3 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid multiple page redirects Potential savings of 210 ms
Redirects introduce additional delays before the page can be loaded
Speed Index 2.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 40 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce the impact of third-party code Third-party code blocked the main thread for 420 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 16 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
Time to Interactive 3.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoid long main-thread tasks 15 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Largest Contentful Paint element 3,190 ms
This is the largest contentful element painted within the viewport
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport

Mobile

Mobile Screenshot
Avoid multiple page redirects Potential savings of 770 ms
Redirects introduce additional delays before the page can be loaded
Minimize main-thread work 4.6 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 660 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
Largest Contentful Paint 13.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce unused JavaScript Potential savings of 587 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 450 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,031 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve images in next-gen formats Potential savings of 349 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Initial server response time was short Root document took 390 ms
Keep the server response time for the main document short because all other requests depend on it
Speed Index 7.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid an excessive DOM size 2,617 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)
Reduce unused CSS Potential savings of 98 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Time to Interactive 13.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint 4.1 s
First Contentful Paint marks the time at which the first text or image is painted
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)
Max Potential First Input Delay 490 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint element 13,000 ms
This is the largest contentful element painted within the viewport
Properly size images Potential savings of 415 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Cumulative Layout Shift 0.454
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Defer offscreen images Potential savings of 4 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Preload Largest Contentful Paint image Potential savings of 630 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP
Network Round Trip Times 20 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
Reduce JavaScript execution time 2.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks 15 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve static assets with an efficient cache policy 21 resources found
A long cache lifetime can speed up repeat visits to your page
Efficiently encode images Potential savings of 229 KiB
Optimized images load faster and consume less cellular data
Document uses legible font sizes 98.87% 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
Total Blocking Time 1,200 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Server Backend Latencies 30 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 chaining critical requests 16 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
Warning! Your description is not 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
Warning! Your website is not SSL secured (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
Warning! You have broken links View links
First 20 Links Relationship HTTP Status
E-wheels logo_ Blue color 75CDD8.png Internal Link 404
FR Internal Link 404
IT Internal Link 404
E-Bike Internal Link 404
E-Scooter Internal Link 404
Zubehör Internal Link 404
Zubehör für E-Bike Internal Link 404
Schloss, Ton und Licht Internal Link 404
Reifen und Schläuche Internal Link 404
Fahrradträger Internal Link 404
Kindersitz Internal Link 404
Helm Internal Link 404
Taschen und Beutel Internal Link 404
Spikereifen Internal Link 404
Zubehör für E-Scooter Internal Link 404
Ersatzteile Internal Link 404
Ersatzteile für E-Bike Internal Link 404
Ersatzteile für E-Scooter Internal Link 404
VERTRIEB Internal Link 404
Kundenservice Internal Link 404

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 301 
date: Thu, 13 Mar 2025 09:12:29 GMT
content-type: text/html; charset=UTF-8
location: https://www.ewheels.ch/de-ch/e-scooter/
set-cookie: ARRAffinity=2a8b4b1234f421a03d9b20b6566bd961158b33bd5aa99b3f1ad2aac2f382ce9c;Path=/;HttpOnly;Secure;Domain=www.ewheels.ch
set-cookie: ARRAffinitySameSite=2a8b4b1234f421a03d9b20b6566bd961158b33bd5aa99b3f1ad2aac2f382ce9c;Path=/;HttpOnly;SameSite=None;Secure;Domain=www.ewheels.ch
x-frame-options: SAMEORIGIN
x-ua-compatible: IE=Edge,chrome=1
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 91fa68f13abf58de-TXL
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A e-wheels.ch 92.205.97.216 IN 10715
NS e-wheels.ch ns31.domaincontrol.com IN 3600
NS e-wheels.ch ns32.domaincontrol.com IN 3600
MX e-wheels.ch mail.e-wheels.ch IN 3600
TXT e-wheels.ch google-site-verification=eQqG0hhYZGpXmNCNtQFxwo9TVA4i__01Mrhkz4GhpbE IN 3600
TXT e-wheels.ch v=spf1 a mx ptr include:secureserver.net ~all IN 3600

About Us

Contact Info

Follow Us

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