Your Website Score is

Similar Ranking

31
GYMBEAM - OBCHOD S DOPLNKAMI VÝŽIVY PRE ŠPORTOVCOV
gymbeam.sk
31
VFILMES
vfilmes.net
31
// KRNL.TO
krnl.to
31
TIKTOK DOWNLOADER - DOWNLOAD VIDEO TIKTOK WITHOUT WATERMARK - SNAPTIK
ssnaptik.app
31
DOOR HANDLE COMPANY | DOOR HANDLE & DOOR FURNITURE SPECIALISTS
doorhandlecompany.co.uk
31
CLUB BÀSQUET VILATORRADA BLOG - CLUB ESPORTIU AMATEUR DE BÀSQUET
cbvilatorrada.cat
31
RADIO TAXI NUMBERS IN CANADA | CAB DIRECTORY - RADIO TAXICAB
radio-taxi-cab.com

Latest Sites

14
HOME | SHIFT - HR CRISIS MANAGEMENT - EMPLOYEE RELATIONS AND HR CONSULTANCY - FAIRNESS & ETHICS CONSULTANCY
shiftperception.co.uk
99
YOUTUBE
m.youtube.com
2
YOUTUBE
youtu.be

Top Technologies

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

31 vanyan.co Last Updated: 1 day

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

Desktop

Mobile

Performance Desktop Score 77%
Best Practices Desktop Score 78%
SEO Desktop Score 100%
Performance Mobile Score 59%
Best Practices Mobile Score 79%
SEO Mobile Score 100%
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 13 Characters
HOME - VANYAN
Meta Description 222 Characters
Welcome to VANYAN, a trans-media production company based in New York City. In Haiti, the word “vanyan” means ‘valiant’, a quality that we take pride in and aim to foster in everything we do, and every client we work with.
Effective URL 17 Characters
https://vanyan.co
Excerpt Page content
HOME - Vanyan Skip to content ...
Keywords Cloud Density
vanyan10 services7 production6 contact4 video4 content4 media4 quality4 work3 create3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
vanyan 10
services 7
production 6
contact 4
video 4
content 4
media 4
quality 4
work 3
create 3
Google Preview Your look like this in google search result
HOME - VANYAN
https://vanyan.co
Welcome to VANYAN, a trans-media production company based in New York City. In Haiti, the word “vanyan” means ‘valiant’, a quality that we take pride
Robots.txt File No Found
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~200.75 KB
Code Size: ~57.2 KB
Text Size: ~143.55 KB Ratio: 71.51%

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
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
Preload Largest Contentful Paint image Est savings of 60 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP
Avoids an excessive DOM size 366 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)
Largest Contentful Paint 1.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Some third-party resources can be lazy loaded with a facade 1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required
User Timing marks and measures 31 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Time to Interactive 3.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Uses third-party cookies 4 cookies found
Third-party cookies may be blocked in some contexts
Reduce unused JavaScript Est savings of 534 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid serving legacy JavaScript to modern browsers Est savings of 12 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
Max Potential First Input Delay 180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Improve image delivery Est savings of 305 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Initial server response time was short Root document took 410 ms
Keep the server response time for the main document short because all other requests depend on it
Speed Index 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce unused CSS Est savings of 220 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid chaining critical requests 44 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
Total Blocking Time 270 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid enormous network payloads Total size was 4,640 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 2.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Legacy JavaScript Est savings of 30 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
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
Minify CSS Est savings of 3 KiB
Minifying CSS files can reduce network payload sizes
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
Serve static assets with an efficient cache policy 60 resources found
A long cache lifetime can speed up repeat visits to your page
Defer offscreen images Est savings of 3 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
JavaScript execution time 1.1 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.7 s
First Contentful Paint marks the time at which the first text or image is painted
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
Use efficient cache lifetimes Est savings of 1,664 KiB
A long cache lifetime can speed up repeat visits to your page
Reduce the impact of third-party code Third-party code blocked the main thread for 450 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 element 1,740 ms
This is the largest contentful element painted within the viewport

Mobile

Mobile Screenshot
Legacy JavaScript Est savings of 29 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
Some third-party resources can be lazy loaded with a facade 1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required
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
Reduce unused CSS Est savings of 244 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
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)
Speed Index 6.4 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Improve image delivery Est savings of 305 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Defer offscreen images Est savings of 1,536 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Minify CSS Est savings of 3 KiB
Minifying CSS files can reduce network payload sizes
First Contentful Paint 2.3 s
First Contentful Paint marks the time at which the first text or image is painted
Uses third-party cookies 4 cookies found
Third-party cookies may be blocked in some contexts
Avoid enormous network payloads Total size was 4,842 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint element 7,650 ms
This is the largest contentful element painted within the viewport
Eliminate render-blocking resources Est savings of 1,130 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Time to Interactive 19.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
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
Avoid serving legacy JavaScript to modern browsers Est savings of 12 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
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
Avoid chaining critical requests 44 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
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
User Timing marks and measures 44 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Serve static assets with an efficient cache policy 60 resources found
A long cache lifetime can speed up repeat visits to your page
Reduce the impact of third-party code Third-party code blocked the main thread for 570 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 7.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Avoids an excessive DOM size 366 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)
Preload Largest Contentful Paint image Est savings of 560 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP
Initial server response time was short Root document took 450 ms
Keep the server response time for the main document short because all other requests depend on it
Use efficient cache lifetimes Est savings of 1,664 KiB
A long cache lifetime can speed up repeat visits to your page
Cumulative Layout Shift 0.022
Cumulative Layout Shift measures the movement of visible elements within the viewport
Server Backend Latencies 20 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
Total Blocking Time 350 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce unused JavaScript Est savings of 676 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease 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
Warning! Your description is not optimized
Robots.txt
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not 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
Congratulations! Your site not 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

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
vanyan.co Already Registered
vanyan.us Available
vanyan.com Already Registered
vanyan.org Available
vanyan.net Available
vnyan.co Available
fanyan.co Available
tanyan.co Available

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, 12 Jun 2025 14:52:04 GMT
Server: Apache
Link: ; rel="https://api.w.org/", ; rel="alternate"; title="JSON"; type="application/json", ; rel=shortlink
Upgrade: h2,h2c
Connection: Upgrade
host-header: c2hhcmVkLmJsdWVob3N0LmNvbQ==
Content-Type: text/html; charset=UTF-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records