Your Website Score is

Similar Ranking

2
CANVA
canva.com
2
h.k.p.com
2
MSN
msn.com
2
320ytmp3.com.
2
---HUBER.CO - THIS WEBSITE IS FOR SALE! - ---HUBER RESOURCES AND INFORMATION.
beegcom.club
2
JUST A MOMENT...
kinks.ca
2
mauropozzer.com

Latest Sites

19
SENILE TEAM DEV LOG
senileteam.com
14
BOXHERO.IN
boxhero.in
21
HUYCHESS
huychess.sbs
96
YOUTUBE
youtu.be
9
YOUTUBE
youtube.com
19
YUPPOW - FREE HD MOVIES AND TV SHOWS STREAMING ONLINE
yuppow.org
14
-
coloressence.com

Top Technologies

Google Font API
Font Scripts
Nginx
Web Servers
jQuery
JavaScript Frameworks
CloudFlare
CDN
PHP
Programming Languages
Varnish
Cache Tools
Google Tag Manager
Tag Managers
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks
WordPress
CMS

2 ssassa.ch Last Updated: 1 week

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

Desktop

Mobile

Performance Desktop Score 78%
Best Practices Desktop Score 0%
SEO Desktop Score 92%
Performance Mobile Score 58%
Best Practices Mobile Score 100%
SEO Mobile Score 92%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 19 Characters
STARTSEITE - SSASSA
Meta Description 0 Characters
NO DATA
Effective URL 21 Characters
https://www.ssassa.ch
Excerpt Page content
Startseite - SSASSA SSASSA Start Portrait...
Keywords Cloud Density
galerie45 ssassa23 musik10 flamenco9 schulhauskonzerte8 schutzkonzept7 übersicht6 videos6 workshops6 presse6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
galerie 45
ssassa 23
musik 10
flamenco 9
schulhauskonzerte 8
schutzkonzept 7
übersicht 6
videos 6
workshops 6
presse 6
Google Preview Your look like this in google search result
STARTSEITE - SSASSA
https://www.ssassa.ch
Startseite - SSASSA SSASSA Start Portrait...
Robots.txt File Detected
http://ssassa.ch/robots.txt
Sitemap.xml File Detected
http://ssassa.ch/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~136.48 KB
Code Size: ~101.45 KB
Text Size: ~35.03 KB Ratio: 25.67%

Social Data

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Time to Interactive 2.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element 2,460 ms
This is the largest contentful element painted within the viewport
Eliminate render-blocking resources Est savings of 350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minify JavaScript Est savings of 60 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Reduce unused JavaScript Est savings of 356 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid an excessive DOM size 853 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 Est savings of 10 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
Speed Index 3.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Document request latency Est savings of 510 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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
Use efficient cache lifetimes Est savings of 263 KiB
A long cache lifetime can speed up repeat visits to your page
Minimize main-thread work 2.6 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 230 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint 2.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Improve image delivery Est savings of 903 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Serve static assets with an efficient cache policy 74 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid enormous network payloads Total size was 2,966 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests 60 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
Cumulative Layout Shift 0.015
Cumulative Layout Shift measures the movement of visible elements within the viewport
Font display Est savings of 240 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).
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
Total Blocking Time 100 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minimize third-party usage Third-party code blocked the main thread for 20 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 50 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
Render blocking requests Est savings of 630 ms
Requests are blocking the page's initial render, which may delay LCP
JavaScript execution time 1.0 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 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)
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Legacy JavaScript Est savings of 10 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

Mobile

Mobile Screenshot
Avoid chaining critical requests 60 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
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
Reduce unused JavaScript Est savings of 357 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Reduce unused CSS Est savings of 212 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Use efficient cache lifetimes Est savings of 264 KiB
A long cache lifetime can speed up repeat visits to your page
Reduce JavaScript execution time 1.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Serve images in next-gen formats Est savings of 372 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
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)
Minimize main-thread work 3.4 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 853 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)
Time to Interactive 11.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Document uses legible font sizes 99.78% 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
Max Potential First Input Delay 110 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Serve static assets with an efficient cache policy 74 resources found
A long cache lifetime can speed up repeat visits to your page
Total Blocking Time 160 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Server Backend Latencies 120 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
Largest Contentful Paint 11.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
Minify CSS Est savings of 18 KiB
Minifying CSS files can reduce network payload sizes
Speed Index 9.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Render blocking requests Est savings of 2,720 ms
Requests are blocking the page's initial render, which may delay LCP
First Contentful Paint 3.6 s
First Contentful Paint marks the time at which the first text or image is painted
Cumulative Layout Shift 0.021
Cumulative Layout Shift measures the movement of visible elements within the viewport
Initial server response time was short Root document took 300 ms
Keep the server response time for the main document short because all other requests depend on it
Font display Est savings of 520 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).
Improve image delivery Est savings of 1,044 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Eliminate render-blocking resources Est savings of 2,650 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Properly size images Est savings of 811 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Minimize third-party usage Third-party code blocked the main thread for 30 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
Legacy JavaScript Est savings of 10 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
Minify JavaScript Est savings of 60 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Document request latency Est savings of 680 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Avoid enormous network payloads Total size was 2,968 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid long main-thread tasks 8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint element 11,510 ms
This is the largest contentful element painted within the viewport
Avoid serving legacy JavaScript to modern browsers Est savings of 10 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

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
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
SSASSA Internal Link 200
Start Internal Link 200
Portrait Internal Link 200
MusikerInnen Internal Link 200
Tänzerinnen Internal Link 200
Flamenco Ektaal Internal Link 200
Musaik Internal Link 200
Verein WOW Internal Link 200
Links Internal Link 200
Schulkonzerte Internal Link 200
Schnabelwetzer Internal Link 200
Workshops – Projekttage Internal Link 200
Franzastisch Internal Link 200
¡Let´s sing oise Song! Internal Link 200
Germanofolies Internal Link 200
The Road of the Gypsies Internal Link 200
Flamenco – von Sevilla bis Jajpur Internal Link 200
Subvention Internal Link 200
Tourneeliste Schulhauskonzerte Internal Link 200
Feedbacks – Presse Internal Link 200

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
ssassa.co Available
ssassa.us Available
ssassa.com Available
ssassa.org Available
ssassa.net Already Registered
sassa.ch Already Registered
wsassa.ch Available
xsassa.ch Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/1.1 200 OK
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding, Cookie
Cache-Control: max-age=3, must-revalidate
Last-Modified: Sun, 28 Sep 2025 12:53:22 GMT
Content-Length: 23378
Date: Sun, 28 Sep 2025 13:07:03 GMT
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A ssassa.ch 149.126.4.101 IN 14221
NS ssassa.ch ns2.cyon.ch IN 21600
NS ssassa.ch ns1.cyon.ch IN 21600
MX ssassa.ch mail.ssassa.ch IN 14400
TXT ssassa.ch v=spf1 include:appriver.com include:spf.protection.cyon.net -all IN 14400
AAAA ssassa.ch 2a01:ab20::4:0:0:0:101 IN 14400

About Us

We provide SEO metrics for your website. There are many who have trusted on us and improved their position thanks to our recommendations

Contact Info

RYIN
10407 Feeney Trafficway Apt. 577
Maryland Line
1-760-992-3170
[email protected]

Follow Us

Facebook
© Copyright 2023
Languages | English