sonder.com score is

Top Technologies
CloudFlare
CDN
Google Font API
Font Scripts
WordPress
CMS
Nginx
Web Servers
Font Awesome
Font Scripts
Apache
Web Servers
Twitter Bootstrap
Web Frameworks
Google Tag Manager
Tag Managers

37 sonder.com Last Updated: 3 years

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

Desktop Speed Score

Mobile Speed Score

Performance Desktop Score 81%
Best Practices Desktop Score 87%
SEO Desktop Score 75%
Progressive Web App Desktop Score 73%
Performance Mobile Score 23%
Best Practices Mobile Score 80%
SEO Mobile Score 76%
Progressive Web App Mobile Score 75%
Page Authority Authority 41%
Domain Authority Domain Authority 56%
Moz Rank 4.1/10
Bounce Rate Rate 0%
Title Tag 30 Characters
SONDER | A BETTER WAY TO STAY.
Meta Description 75 Characters
Sonder - a new way to stay in your favorite neighborhoods around the world.
Effective URL 22 Characters
https://www.sonder.com
Google Preview Your look like this in google search result
SONDER | A BETTER WAY TO STAY.
https://www.sonder.com
Sonder - a new way to stay in your favorite neighborhoods around the world.
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~9.7 KB
Code Size: ~9.2 KB
Text Size: ~507 B Ratio: 5.11%

sonder.com 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 Speed Score

Desktop Screenshot
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 large layout shifts 3 elements found
These DOM elements contribute most to the CLS of the page.
Remove unused JavaScript Potential savings of 481 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoid serving legacy JavaScript to modern browsers Potential savings of 25 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
Total Blocking Time 200 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Time to Interactive 2.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
JavaScript execution time 0.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoid an excessive DOM size 1,052 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
robots.txt is not valid 324 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Estimated Input Latency 20 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Keep request counts low and transfer sizes small 92 requests • 2,403 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
Initial server response time was short Root document took 520 ms
Keep the server response time for the main document short because all other requests depend on it
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid chaining critical requests 3 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 2.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve static assets with an efficient cache policy 27 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids enormous network payloads Total size was 2,403 KiB
Large network payloads cost users real money and are highly correlated with long load times
Max Potential First Input Delay 250 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minimizes main-thread work 1.6 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 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Preload Largest Contentful Paint image Potential savings of 310 ms
Preload the image used by the LCP element in order to improve your LCP time
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
First CPU Idle 2.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
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
Remove unused CSS Potential savings of 48 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Properly size images Potential savings of 428 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Eliminate render-blocking resources Potential savings of 80 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Mobile Speed Score

Mobile Screenshot
Max Potential First Input Delay 1,040 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
robots.txt is not valid 324 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Serve static assets with an efficient cache policy 27 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint 2.3 s
First Contentful Paint marks the time at which the first text or image is painted
First Contentful Paint (3G) 4658 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.53% 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 CPU Idle 14.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Time to Interactive 17.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Speed Index 9.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Keep request counts low and transfer sizes small 89 requests • 2,161 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Total Blocking Time 2,130 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid serving legacy JavaScript to modern browsers Potential savings of 25 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
Avoids enormous network payloads Total size was 2,161 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 7.0 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 590 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 1,055 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)
Cumulative Layout Shift 0.014
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Meaningful Paint 4.3 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid long main-thread tasks 18 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Estimated Input Latency 450 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
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
Largest Contentful Paint 8.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Initial server response time was short Root document took 560 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid chaining critical requests 3 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
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
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
Avoid large layout shifts 2 elements found
These DOM elements contribute most to the CLS of the page.
Eliminate render-blocking resources Potential savings of 390 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce JavaScript execution time 4.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 408 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Remove unused CSS Potential savings of 47 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
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
Remove unused JavaScript Potential savings of 470 KiB
Remove unused JavaScript to reduce bytes consumed by network activity

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
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
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

sonder.com Alexa Rank

99,999,999

Global Rank

99,999,999

-

Domain Available

Domain (TDL) and Typo Status
sonder.co Available Buy Now!
sonder.us Available Buy Now!
sonder.com Available Buy Now!
sonder.org Available Buy Now!
sonder.net Available Buy Now!
snder.com Available Buy Now!
wonder.com Available Buy Now!
xonder.com Available Buy Now!

Information Server sonder.com

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
date: Sun, 09 May 2021 18:28:14 GMT
content-type: text/html; charset=utf-8
set-cookie: __cfduid=d4b8eacf57cfec2160e9592e857d878031620584894; expires=Tue, 08-Jun-21 18:28:14 GMT; path=/; domain=.sonder.com; HttpOnly; SameSite=Lax; Secure
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
x-download-options: noopen
x-permitted-cross-domain-policies: none
referrer-policy: strict-origin-when-cross-origin
x-csrf-token: URu4AakexX7S0CeV2ugkQg/HLqHTsNwt5/C8TsEyRumYbQinQKZwI1cpLuaj/JzddjSN+tcPKcsB8fPdSn9/tg==
cache-control: max-age=0, private, must-revalidate
set-cookie: experiment_target_key=7042048c-0931-45d2-b690-ba46fbed732e; domain=sonder.com; path=/; secure
set-cookie: X-CSRF-Token=Tx7wSzGvCEa2R7NBpJpGE3mGnJdLBvQS%2FBmhEUrN%2Fl%2BGaEDt2Be9GzO%2BujLdjv6MAHU%2FzE%2B5AfQaGO6CwYDHAA%3D%3D; path=/; secure
set-cookie: _sndr_session_production=QitvUE85bjNMWStvTy8vUWsvMlVKd3R2blNtUkdNZzlLUysva3RrYjE3cm9lVDdPaFdlT2hsekpIajNnUHJJZG5qcThsWVd6bjZyOWNxTXp6YXFNTVNJVk5pNEwrQ25rMjlYSjY1dlVtM2hkN05hVU16UlhrZmZQT3ovQ1JKUnlaZ2hzb1k5bTJ6c2s3bFJuQy9XTWY5N0FOaklsempYcWxQVXpxcXkzOFZFVEtpWXhFdzZ1SG5lMU9Vd0pqK1N6VGZZdy8yMmNRTUdabEtiRWJGZ3FoQkFkK3EyUDlQc2RZQ0NJYlBoSTVwZWFIc3dwNnMyNVpXWWRMOFg3bENYeEJmaEZqM1NLaU5JVWFxbVBlaHJCMk10Uk1tUFhhQ25kS1VOOGNZNjFKbnh6TGxVSFNsd3pBZ1JpY0hrVmtvYTlJVTZWLzh5aWprbU1SY3ZIeHNOMCt3PT0tLU9SS2tMcVVqaVF2cDhaTlBTTnRHWkE9PQ%3D%3D--9c05c822a5e9a2964fa333fd39f583e26d722ffc; domain=.sonder.com; path=/; secure; HttpOnly
x-request-id: 9aa4e785-b394-9a77-9cc8-7fec7f73d831
x-runtime: 0.037799
strict-transport-security: max-age=2592000; includeSubDomains; preload
vary: Origin
x-envoy-upstream-service-time: 41
cf-cache-status: DYNAMIC
cf-request-id: 09f3fc2776000021817d024000000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 64ccfc858cf22181-DUS
content-encoding: gzip
DNS Records DNS Resource Records associated with a hostname
sonder.com View DNS Records

Social Data