Your SEO.rip Score is

Similar Ranking

46
CBD Oil - Don't Buy It Until You Know What You're Getting Into
cbdexpertz.com
46
X-D.ME URL SHORTENER
x-d.me
46
ИНТЕРНЕТ-МАГАЗИН КАРНАВАЛЬНЫХ КОСТЮМОВ И АКСЕССУАРОВ К НИМ
karnavalnoe.info
44
ECO FRIENDLY HOME, CUSTOM MASKS, HOME SECURITY, PC GAMING PRODUCTS – FANCY.TOYS
fancy.toys
41
BACK2GAMING
back2gaming.com
39
#1 WonderDoc® | Top Ranked EHR and PM software for Chiropractors
wonderdoc.com
36
Fancy.shoes
fancy.shoes

Latest Sites

46
ИНТЕРНЕТ-МАГАЗИН КАРНАВАЛЬНЫХ КОСТЮМОВ И АКСЕССУАРОВ К НИМ
karnavalnoe.info

Top Technologies

Google Font API
Font Scripts
WordPress
CMS
CloudFlare
CDN
Font Awesome
Font Scripts
Nginx
Web Servers
Yoast SEO
SEO
Google Tag Manager
Tag Managers
YouTube
Video Players
Twitter Bootstrap
Web Frameworks

46 x-d.me Last Updated: 4 weeks

Success 70% of passed verification steps
Warning 15% of total warnings
Errors 15% of total errors, require fast action

Desktop:

Mobile:

Performance Desktop Score 95%
Best Practices Desktop Score 92%
SEO Desktop Score 100%
PWA Desktop Score 22%
Performance Mobile Score 44%
Best Practices Mobile Score 85%
SEO Mobile Score 97%
PWA Mobile Score 30%
Page Authority Authority 23%
Domain Authority: Domain Authority: 5%
Moz Rank: 2.3/10
Bounce Rate: Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 20 Characters
X-D.ME URL SHORTENER
Meta Description 83 Characters
Shorten your links with click analytics and more. Free and paid accounts available.
Effective URL 14 Characters
https://x-d.me
Excerpt Page content
x-d.me URL Shortener Toggle navigation ...
Keywords Cloud: Density
shortener4 clicks2 home2 urls2 total2 contact1 views1 other1 data1 stats1
Keyword Consistency Keyword density
Keyword Frequency Title Desc Domain H1 H2
shortener 4
clicks 2
home 2
urls 2
total 2
contact 1
views 1
other 1
data 1
stats 1
Google Preview How this page looks in Google SERP
X-D.ME URL SHORTENER
https://x-d.me
Shorten your links with click analytics and more. Free and paid accounts available.
Robots.txt File Detected
Sitemap File Detected
Page Size Code to Text Ratio
Document Size: ~10.46 KB
Code Size: ~7.76 KB
Text Size: ~2.7 KB Ratio: 25.80%

Social Data

Only Registered Users

Sign up to see all features and reviews about this site

Login

Estimated 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
Annual
4,704
Pages Views
Annual
$0
Income
Annual

Technologies

Only Registered Users

Sign up to see all features and reviews about this site

Login

PWA - Manifest

Manifest is not valid
Your site doesnt have a valid manifest.json, read more in Web App Manifest

Desktop:

Desktop Screenshot
Cumulative Layout Shift 0.01
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce unused JavaScript Potential savings of 165 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Max Potential First Input Delay 120 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Serve static assets with an efficient cache policy 17 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid non-composited animations 10 animated elements found
Animations which are not composited can be janky and increase CLS
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Initial server response time was short Root document took 150 ms
Keep the server response time for the main document short because all other requests depend on it
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
Avoids enormous network payloads Total size was 1,344 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Includes front-end JavaScript libraries with known security vulnerabilities 9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid large layout shifts 3 elements found
These DOM elements contribute most to the CLS of the page.
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
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint 1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Time to Interactive 2.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Total Blocking Time 70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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 long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Keep request counts low and transfer sizes small 60 requests • 1,344 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid chaining critical requests 17 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
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoids an excessive DOM size 150 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)
Reduce unused CSS Potential savings of 44 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Eliminate render-blocking resources Potential savings of 40 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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

Mobile:

Mobile Screenshot
Includes front-end JavaScript libraries with known security vulnerabilities 9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Initial server response time was short Root document took 120 ms
Keep the server response time for the main document short because all other requests depend on it
First Meaningful Paint 2.9 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint 2.8 s
First Contentful Paint marks the time at which the first text or image is painted
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Keep request counts low and transfer sizes small 62 requests • 1,361 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid chaining critical requests 18 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 element 1 element found
This is the largest contentful element painted within the viewport
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
Total Blocking Time 2,120 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve static assets with an efficient cache policy 17 resources found
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 12.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Reduce the impact of third-party code Third-party code blocked the main thread for 1,770 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 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
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 Contentful Paint (3G) 5490 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Reduce JavaScript execution time 5.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Eliminate render-blocking resources Potential savings of 1,780 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce unused CSS Potential savings of 44 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Document uses legible font sizes 98.94% 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
Largest Contentful Paint 4.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce unused JavaScript Potential savings of 165 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Speed Index 4.6 s
Speed Index shows how quickly the contents of a page are visibly populated
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 not sized appropriately 75% 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
Avoids enormous network payloads Total size was 1,361 KiB
Large network payloads cost users real money and are highly correlated with long load times
Max Potential First Input Delay 600 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids an excessive DOM size 146 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)

SEO Tips

Only Registered Users

Sign up to see all features and reviews about this site

Login

Alexa Rank

Only Registered Users

Sign up to see all features and reviews about this site

Login

Domain Availability

Domains and Typos Status
x-d.co Already Registered
x-d.us Available Buy this domain now!
x-d.com Already Registered
x-d.org Already Registered
x-d.net Already Registered
xd.me Available Buy this domain now!
s-d.me Available Buy this domain now!
e-d.me Already Registered

Server Info

Only Registered Users

Sign up to see all features and reviews about this site

Login