Your Website Score is

Similar Ranking

14
KRISENVORSORGE MIT VORSORGE.WIKI | VORSORGE.WIKI
vorsorge.wiki
14
PRESSE.WS – PRESSEMELDUNGEN
presse.ws
14
ОФОРМЛЕНИЕ СВАДЕБ ЦВЕТАМИ, СВАДЕБНЫЙ БУКЕТ НЕВЕСТЫ, СВАДЕБНАЯ ФЛОРИСТИКА, НОВОГОДНИЕ УКРАШЕНИЕ ПОМЕЩЕНИЙ ЮЗАО МОСКВА
creativebouquet.ru
14
BEZAHLBARE KUNST KAUFEN BEI PARANORMAL PICTURES MONOCHROME MALEREI UVM
paranormal-pictures.de
14
HOME - MALEREIBETRIEB OLEJNIK
malereibetrieb.eu
14
STARTSEITE - GREENSTARSHOP
greenstarshop.ch
14
PAPP-PALETTEN PRONATIVO – PALETTEN AUS PAPPE
papp-paletten.com

Latest Sites

14
PAPP-PALETTEN PRONATIVO – PALETTEN AUS PAPPE
papp-paletten.com
16
BIOBAY.DE
biobay.de
26
MESSAGE.WS – PRESSEMELDUNGEN
message.ws
58
IDEALO – DIE NR. 1 IM PREISVERGLEICH
idealo.de
31
TAXI TÜBINGEN STUTTGART | RENNA - TAXISERVICE, KURIERDIENST & FLUGHAFENTRANSFER TÜBINGEN
taxista.de
14
BEZAHLBARE KUNST KAUFEN BEI PARANORMAL PICTURES MONOCHROME MALEREI UVM
paranormal-pictures.de
6
RATGEBER MIT FRAGEN UND ANTWORTEN ZU VIELEN THEMEN
www.meinefragen.net

Top Technologies

Apache
Web Servers
Google Font API
Font Scripts
WordPress
CMS
Nginx
Web Servers
CloudFlare
CDN
Font Awesome
Font Scripts
Google AdSense
Advertising Networks
Twitter Bootstrap
Web Frameworks

14 greenstarshop.ch Last Updated: 3 days

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

Desktop

Mobile

Performance Desktop Score 86%
Best Practices Desktop Score 100%
SEO Desktop Score 83%
PWA Desktop Score 33%
Performance Mobile Score 59%
Best Practices Mobile Score 100%
SEO Mobile Score 83%
PWA Mobile Score 40%
Page Authority Authority 3%
Domain Authority Domain Authority 2%
Moz Rank 0.3/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 26 Characters
STARTSEITE - GREENSTARSHOP
Meta Description 0 Characters
NO DATA
Effective URL 24 Characters
https://greenstarshop.ch
Excerpt Page content
Startseite - Greenstarshop ...
Keywords Cloud Density
produkte11 blüten9 versandkosten8 zzgl8 produkt8 lieferzeit7 tage7 solubilisat7 warenkorb6 fragen5
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
produkte 11
blüten 9
versandkosten 8
zzgl 8
produkt 8
lieferzeit 7
tage 7
solubilisat 7
warenkorb 6
fragen 5
Google Preview Your look like this in google search result
STARTSEITE - GREENSTARSHOP
https://greenstarshop.ch
Startseite - Greenstarshop ...
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~140.28 KB
Code Size: ~118.97 KB
Text Size: ~21.31 KB Ratio: 15.19%

Estimation Traffic and Earnings

37
Unique Visits
Daily
68
Pages Views
Daily
$0
Income
Daily
1,036
Unique Visits
Monthly
1,938
Pages Views
Monthly
$0
Income
Monthly
11,988
Unique Visits
Yearly
22,848
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
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 Potential savings of 500 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
Reduce unused CSS Potential savings of 137 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
Cumulative Layout Shift 0.025
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint 1.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce initial server response time Root document took 1,480 ms
Keep the server response time for the main document short because all other requests depend on it
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Serve images in next-gen formats Potential savings of 515 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 Potential savings of 196 KiB
Optimized images load faster and consume less cellular data
Avoid serving legacy JavaScript to modern browsers Potential savings of 10 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
Avoid chaining critical requests 75 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
Keep request counts low and transfer sizes small 116 requests • 1,677 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids an excessive DOM size 771 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)
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
Time to Interactive 1.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Defer offscreen images Potential savings of 3 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Total Blocking Time 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids enormous network payloads Total size was 1,677 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve static assets with an efficient cache policy 108 resources found
A long cache lifetime can speed up repeat visits to your page
Properly size images Potential savings of 307 KiB
Serve images that are appropriately-sized to save cellular data and improve load time

Mobile

Mobile Screenshot
Minimize main-thread work 2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 1 element found
These DOM elements contribute most to the CLS of the page.
Defer offscreen images Potential savings of 114 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Time to Interactive 7.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Reduce initial server response time Root document took 1,410 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint 3.7 s
First Contentful Paint marks the time at which the first text or image is painted
Serve images in next-gen formats Potential savings of 492 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Speed Index 5.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Keep request counts low and transfer sizes small 107 requests • 1,515 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
Avoid chaining critical requests 76 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 an excessive DOM size 885 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)
Tap targets are not sized appropriately 73% 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
Reduce unused CSS Potential savings of 149 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
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
Efficiently encode images Potential savings of 158 KiB
Optimized images load faster and consume less cellular data
Avoid serving legacy JavaScript to modern browsers Potential savings of 10 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
Document uses legible font sizes 100% 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
First Meaningful Paint 3.7 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint 6.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve static assets with an efficient cache policy 100 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint (3G) 7302 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Max Potential First Input Delay 160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Total Blocking Time 110 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids enormous network payloads Total size was 1,515 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Eliminate render-blocking resources Potential savings of 2,470 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
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
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.

Alexa Rank

0

Local Rank: / Users: / PageViews:

12,720,126

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: Thu, 30 Jun 2022 22:24:10 GMT
Server: Apache
Set-Cookie: wc_postfinancecheckout_device_id=2599b1fe-0cd2-4e2d-9cc0-6310c2716d46; expires=Fri, 30-Jun-2023 22:24:10 GMT; Max-Age=31536000; path=/
Link: ; rel="https://api.w.org/"
Link: ; rel="alternate"; type="application/json"
Link: ; rel=shortlink
Content-Encoding: gzip
Vary: Accept-Encoding
Strict-Transport-Security: max-age=16000000
Upgrade: h2
Connection: Upgrade
Content-Type: text/html; charset=UTF-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records