Your Website Score is

Similar Ranking

40
CODENAMES - PLAY WITH YOUR FRIENDS ONLINE
codenames.game
40
LATINO-WEBTV.COM -&NBSPLATINO WEBTV RESOURCES AND INFORMATION.
latino-webtv.com
40
40
LIVE TOTAL - WEB SPORTS ONLINE FOR FREE | LIVETOTAL SPORTS
feed4u.me
40
TELUGU MOVIE NEWS ONLINE | | 2017 TELUGU MOVIE LATEST | REVIEWS | TELUGU MOVIE NEWS IN TELUGU | LATEST TELUGU MOVIE NEWS
andhrawatch.com
40
SOLARMOVIE - BEST SITE TO WATCH FREE MOVIES ONLINE AND FREE TV SERIES ONLINE!
solarmovie.id
40
DIGITAL CREDENTIAL SERVICE | PARCHMENT
iwantmytranscript.com

Latest Sites

31
BIDMATE: FREE ONLINE EBAY AUCTION SNIPER
bidmate.co.uk
1
EFLIX - WATCH YOUR FAVORITE MOVIES, ANIMES & CARTOONS ONLINE
eflix.is
1
abigantus.com Website SEO Rank Analysis by SEOWebsiteRank.com
abigantus.com
1
rogers.comhome Website SEO Rank Analysis by SEOWebsiteRank.com
rogers.comhome
26
VIEW PRIVATE INSTAGRAM ACCOUNTS FOR FREE - UNPRIVATE INSTAGRAM
viewpriv.com
1
juanantoniorodriguezmenier.com Website SEO Rank Analysis by SEOWebsiteRank.com
juanantoniorodriguezmenier.com
23
FREE VPN SERVICE — SUPER FREE L2TP VPN ACCOUNTS
superfreevpn.com

Top Technologies

Nginx.png
Nginx
Web Servers
Apache.png
Apache
Web Servers
CloudFlare.png
CloudFlare
CDN
Google%20Font%20API.png
Google Font API
Font Scripts
Font%20Awesome.png
Font Awesome
Font Scripts
WordPress.png
WordPress
CMS
Twitter%20Bootstrap.png
Twitter Bootstrap
Web Frameworks
Microsoft.png
Windows Server
Operating Systems

SEO Rank : 40 Website URL: codenames.game Last Updated: 5 months

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

Estimation Traffic and Earnings

0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly

Desktop

Mobile

Performance Desktop Score 89%
Best Practices Desktop Score 93%
SEO Desktop Score 90%
Progressive Web App Desktop Score 52%
Performance Mobile Score 59%
Best Practices Mobile Score 86%
SEO Mobile Score 92%
Progressive Web App Mobile Score 54%

Moz Authority Rank

Page Authority Authority 33%
Domain Authority Domain Authority 26%
Moz Rank 3.3/10
Bounce Rate Rate 0%

Meta Data

Title Tag 41 Characters
CODENAMES - PLAY WITH YOUR FRIENDS ONLINE
Meta Description 66 Characters
Online game room for playing Codenames - just invite your friends.
Effective URL 22 Characters
https://codenames.game
Excerpt Page content
Codenames - Play with your Friends OnlinePlay with your friends.CREATE ROOMHow to play:1. Click on the CREATE ROOM button2. Choose the language of the word cards and start the game3. Share the room URL with your friends4. Enjoy the game!Vlaada & ...
Keywords Cloud Density
game11 codenames10 play8 room6 online5 many5 czech4 games4 friends4 team4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
game 11
codenames 10
play 8
room 6
online 5
many 5
czech 4
games 4
friends 4
team 4
Google Preview Your look like this in google search result
CODENAMES - PLAY WITH YOUR FRIENDS ONLINE
https://codenames.game
Online game room for playing Codenames - just invite your friends.
Robots.txt File No Found
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~15.57 KB
Code Size: ~12.21 KB
Text Size: ~3.36 KB Ratio: 21.59%

Social Data

Delicious Total: 0
Facebook Total: 10,014
Google Total: 0
Linkedin Total: 0
Pinterest Total: 30
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

Desktop

Desktop Screenshot
Keep request counts low and transfer sizes small 75 requests • 555 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve images in next-gen formats Potential savings of 78 KiB
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
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Minify CSS Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes
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
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused JavaScript Potential savings of 26 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Cumulative Layout Shift 0.054
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid chaining critical requests 4 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
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated
User Timing marks and measures 4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Avoids enormous network payloads Total size was 555 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoids an excessive DOM size 143 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)
Estimated Input Latency 10 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
Serve static assets with an efficient cache policy 51 resources found
A long cache lifetime can speed up repeat visits to your page
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 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 long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimizes main-thread work 0.3 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Properly size images Potential savings of 15 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 2.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First CPU Idle 0.9 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/).
Initial server response time was short Root document took 210 ms
Keep the server response time for the main document short because all other requests depend on it
Time to Interactive 1.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.

Mobile

Mobile Screenshot
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Time to Interactive 5.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Max Potential First Input Delay 220 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
User Timing marks and measures 4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Keep request counts low and transfer sizes small 75 requests • 435 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Remove unused JavaScript Potential savings of 26 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minimizes main-thread work 1.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 4.1 s
First Contentful Paint marks the time at which the first text or image is painted
First CPU Idle 4.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/).
First Meaningful Paint 4.1 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Cumulative Layout Shift 0.284
Cumulative Layout Shift measures the movement of visible elements within the viewport
Initial server response time was short Root document took 20 ms
Keep the server response time for the main document short because all other requests depend on it
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
Eliminate render-blocking resources Potential savings of 780 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minify CSS Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 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
Tap targets are sized appropriately 100% 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
Avoid chaining critical requests 4 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
Minimize third-party usage Third-party code blocked the main thread for 240 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
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 6.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Serve static assets with an efficient cache policy 51 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids an excessive DOM size 143 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)
JavaScript execution time 0.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 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoids enormous network payloads Total size was 435 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index 4.1 s
Speed Index shows how quickly the contents of a page are visibly populated
First Contentful Paint (3G) 8241.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Total Blocking Time 160 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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

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
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
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
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Domain Available

Domain (TDL) and Typo Status
codenames.co Already Registered
codenames.us Already Registered
codenames.com Already Registered
codenames.org Already Registered
codenames.net Already Registered
cdenames.game Already Registered
dodenames.game Already Registered
rodenames.game Already Registered

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
date: Thu, 17 Dec 2020 15:03:05 GMT
content-type: text/html; charset=utf-8
content-disposition: inline; filename="index"
cache-control: public, max-age=0, must-revalidate
access-control-allow-origin: *
etag: W/"c00711caa7fc8124d59c1154ee78c5695faa859a2c9c2c1768c51b5401509c88"
x-vercel-cache: HIT
age: 2363
server: Vercel
x-vercel-id: sfo1::fbdfz-1608217385669-75ac038c51d3
strict-transport-security: max-age=63072000
content-encoding: gzip

View DNS Records

DNS Records DNS Resource Records associated with a hostname
Type Name Value Class TTL

Comments

codenames.game Stats By Traffic Tips Alexa Server Meta Authority Technologies Pagespeed Pagespeed Stats Social Domain Available
Add extension to Chrome