Sayulita.run - SEO Checker

Your Website Score is

Similar Ranking

--- SHOP | TABBU.COM.CO | COLOMBIA

tabbu.com.co

CRISTÓBAL LÓPEZ Y DE SOUSA, LIBRES | LA VOZ

lavoz.com.ar

ESTÉTICA Y COSMIATRÍA -

esteticaycosmiatria.com

AGENCIA DE MARKETING DE CONTENIDOS E INBOUND MARKETING

genwords.com

SAYULITA RUNNING EXPERIENCES

sayulita.run

BITSION | DESARROLLO DE SOFTWARE

bitsion.com

INICIO - TODONEGOCIOSWEB

todonegociosweb.com

Latest Sites

recetas.clarin.com

linixmotor.es

CONSULTORÍA DE RRHH | DOS ARGENTINA

dosargentina.com.ar

ENVÍA PAGOS NACIONALES E INTERNACIONALES | VITAWALLET.IO

vitawallet.io

COMPUESTO CHIMISCO – MY WORDPRESS BLOG

chimisco.com.mx

ENMEDIO ASOCIADOS

enmedioasociados.com

ONCELULAR

oncelular.com.ar

Top Technologies

PHP

Programming Languages

Google Font API

Font Scripts

WordPress

CMS

Apache

Web Servers

Font Awesome

Font Scripts

Yoast SEO

SEO

jQuery

JavaScript Frameworks

Nginx

Web Servers

Twitter Bootstrap

Web Frameworks

Google Tag Manager

Tag Managers

64 sayulita.run Last Updated: 1 year

Success 54% of passed verification steps

Warning 23% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 76%

Best Practices Desktop Score 77%

SEO Desktop Score 100%

Progressive Web App Desktop Score 27%

Performance Mobile Score 12%

Best Practices Mobile Score 77%

SEO Mobile Score 99%

Progressive Web App Mobile Score 30%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 28 Characters

SAYULITA RUNNING EXPERIENCES

Meta Description 350 Characters

How many times did you pack your running shoes and didn't run on your trip? We offer running experiences for traveler who want to run with a local, like a local. Our tours are designed to have you experience the Sayulita region in the purest of ways, running with the knowledge and support of an amazing team. We will take you to the sayulita

Effective URL 24 Characters

https://www.sayulita.run

Excerpt Page content

Sayulita running experiences sayulita.run ...

Keywords Cloud Density

running15 sayulita11 experiences9 miles7 local5 more5 through5 town4 like4 info4

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
running	15
sayulita	11
experiences	9
miles	7
local	5
more	5
through	5
town	4
like	4
info	4

Google Preview Your look like this in google search result

SAYULITA RUNNING EXPERIENCES

https://www.sayulita.run

How many times did you pack your running shoes and didn't run on your trip? We offer running experiences for traveler who want to run with a local,

Robots.txt File Detected

http://sayulita.run/robots.txt

Sitemap.xml File Detected

http://sayulita.run/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~96.59 KB

Code Size: ~70.16 KB

Text Size: ~26.43 KB Ratio: 27.37%

Social Data

Estimation Traffic and Earnings

Unique Visits

Daily

Pages Views

Daily

Income

Daily

Unique Visits

Monthly

Pages Views

Monthly

Income

Monthly

Unique Visits

Yearly

Pages Views

Yearly

Income

Yearly

Technologies

Google Font API

Font Scripts

Squarespace

CMS

PWA - Manifest

Manifest is not valid

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

Desktop

First Meaningful Paint 1.6 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 62 requests • 3,295 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 24 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 160 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 2.9 s

Time to interactive is the amount of time it takes for the page to become fully interactive

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

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 14.1 s

A fast page load over a cellular network ensures a good mobile user experience

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

Remove unused CSS Potential savings of 114 KB

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

Serve images in next-gen formats Potential savings of 574 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

User Timing marks and measures 3 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Server response times are low (TTFB) Root document took 240 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 600 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Efficiently encode images Potential savings of 217 KB

Optimized images load faster and consume less cellular data

Reduce the impact of third-party code Third-party code blocked the main thread for 290 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 330 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time 0.9 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

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

Defer offscreen images Potential savings of 403 KB

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

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 1.8 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 2.7 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input

Avoid enormous network payloads Total size was 3,295 KB

Large network payloads cost users real money and are highly correlated with long load times

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.

First Contentful Paint 1.1 s

First Contentful Paint marks the time at which the first text or image is painted

Minimize Critical Requests Depth 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

Avoids an excessive DOM size 484 elements

Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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)

Mobile

Remove unused CSS Potential savings of 117 KB

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

Serve images in next-gen formats Potential savings of 935 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

User Timing marks and measures 3 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Server response times are low (TTFB) Root document took 460 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 3,440 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Efficiently encode images Potential savings of 219 KB

Optimized images load faster and consume less cellular data

Reduce the impact of third-party code Third-party code blocked the main thread for 2,700 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 2,580 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 5.0 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 587 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to 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

Properly size images Potential savings of 224 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 8.9 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 13.1 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input

Avoid enormous network payloads Total size was 4,994 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 8.4 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

First Contentful Paint 5.8 s

First Contentful Paint marks the time at which the first text or image is painted

Minimize Critical Requests Depth 16 chains found

Avoids an excessive DOM size 484 elements

First Meaningful Paint 8.1 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 63 requests • 4,994 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 25 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 790 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 14.5 s

Time to interactive is the amount of time it takes for the page to become fully interactive

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

Page load is not fast enough on mobile networks Interactive at 14.5 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 450 ms

First Contentful Paint (3G) 11600 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Tap targets are not sized appropriately 93% 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

Document uses legible font sizes 97.57% 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

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 14 Links	Relationship	HTTP Status
sayulita.run	Internal Link	301
http://sayulita.run/search	Internal Link	301
Experiences	Internal Link	301
Partners	Internal Link	301
FAQs	Internal Link	301
Contact	Internal Link	301
https://www.sayulita.run/sayulita-town	Internal Link	200
https://www.sayulita.run/jungle-beaches	Internal Link	200
https://www.sayulita.run/monkey-mountain	Internal Link	200
more info	Internal Link	200
Welcome	Internal Link	301
Introduction	Internal Link	301
Experiences	Internal Link	301
Who we are	Internal Link	301

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Domain Available

Domain (TDL) and Typo	Status
sayulita.co	Already Registered
sayulita.us	Available Buy Now!
sayulita.com	Already Registered
sayulita.org	Already Registered
sayulita.net	Already Registered
syulita.run	Available Buy Now!
wayulita.run	Available Buy Now!
xayulita.run	Available Buy Now!

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/2 200 
date: Wed, 09 Oct 2019 15:02:19 GMT
strict-transport-security: max-age=0
expires: Thu, 01 Jan 1970 00:00:00 GMT
content-type: text/html;charset=utf-8
etag: W/"7fe41277b6b99420f7b988b0599a1b3c--gzip"
content-encoding: gzip
vary: Accept-Encoding
age: 0
set-cookie: crumb=BajmmrUKw+reYTMwZDhiNjNhOGMxZWFmZTk3NzZjOWU1ZTY5NTlj;Path=/
accept-ranges: bytes
x-contextid: 3ebZf1CH/6CTJONVu
server: Squarespace

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	sayulita.run	198.49.23.144	IN	210
A	sayulita.run	198.185.159.145	IN	210
A	sayulita.run	198.185.159.144	IN	210
A	sayulita.run	198.49.23.145	IN	210
NS	sayulita.run	ns37.domaincontrol.com	IN	3600
NS	sayulita.run	ns38.domaincontrol.com	IN	3600

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

64 sayulita.run Last Updated: 1 year

Desktop

Mobile

Social Data

Estimation Traffic and Earnings

Technologies

Google Font API

Squarespace

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Alexa Rank

0

Domain Available

Information Server

About Us

Contact Info

Follow Us