42 aliabdaal.com Last Updated: 3 years

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

Desktop Speed Score

Mobile Speed Score

Performance Desktop Score 88%
Best Practices Desktop Score 87%
SEO Desktop Score 100%
Progressive Web App Desktop Score 36%
Performance Mobile Score 50%
Best Practices Mobile Score 87%
SEO Mobile Score 97%
Progressive Web App Mobile Score 42%
Page Authority Authority 37%
Domain Authority Domain Authority 32%
Moz Rank 3.7/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 10 Characters
ALI ABDAAL
Meta Description 156 Characters
I’m Ali. I’m a doctor, YouTuber and podcaster. On this site we explore the strategies and tools that help us live happier, healthier, more productive lives.
Effective URL 21 Characters
https://aliabdaal.com
Excerpt Page content
Ali Abdaal About Articles Courses Podcast Book Notes Tech Friendzone Hey friends — I’m Ali. I’m a doctor, YouTuber and podcaster. On this site we explore the strategies and tools that help us live happier, healthier, more productive lives. Check out my Ultimate Guides ???? Productivity How to execute efficiently, make time for what matters and ha...
Keywords Cloud Density
notes4 abdaal3 youtuber3 podcast3 friendzone3 time3 youtube2 welcome2 productivity2 successfully2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
notes 4
abdaal 3
youtuber 3
podcast 3
friendzone 3
time 3
youtube 2
welcome 2
productivity 2
successfully 2
Google Preview Your look like this in google search result
ALI ABDAAL
https://aliabdaal.com
I’m Ali. I’m a doctor, YouTuber and podcaster. On this site we explore the strategies and tools that help us live happier, healthier, more productive
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~23.04 KB
Code Size: ~13.77 KB
Text Size: ~9.27 KB Ratio: 40.24%

aliabdaal.com Estimation Traffic and Earnings

3,063
Unique Visits
Daily
5,666
Pages Views
Daily
$4
Income
Daily
85,764
Unique Visits
Monthly
161,481
Pages Views
Monthly
$100
Income
Monthly
992,412
Unique Visits
Yearly
1,903,776
Pages Views
Yearly
$1,056
Income
Yearly

Desktop Speed Score

Desktop Screenshot
Max Potential First Input Delay 190 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid serving legacy JavaScript to modern browsers Potential savings of 9 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 1,357 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests 7 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 Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first 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
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
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
Minify JavaScript Potential savings of 29 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Cumulative Layout Shift 0.196
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
First CPU Idle 2.6 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/).
Minimizes main-thread work 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
Total Blocking Time 200 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Uses efficient cache policy on static assets 4 resources found
A long cache lifetime can speed up repeat visits to your page
JavaScript execution time 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Keep request counts low and transfer sizes small 44 requests • 1,358 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Initial server response time was short Root document took 110 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids an excessive DOM size 200 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)
Remove unused CSS Potential savings of 51 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
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
Time to Interactive 2.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Remove unused JavaScript Potential savings of 691 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Largest Contentful Paint 1.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources Potential savings of 180 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Minimize third-party usage Third-party code blocked the main thread for 210 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
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

Mobile Speed Score

Mobile 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
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
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
Time to Interactive 12.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Speed Index 4.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Estimated Input Latency 250 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
Total Blocking Time 1,310 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Cumulative Layout Shift 0.134
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 3.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Contentful Paint (3G) 4890 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Eliminate render-blocking resources Potential savings of 1,620 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
Remove unused CSS Potential savings of 51 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
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
Keep request counts low and transfer sizes small 44 requests • 1,338 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Max Potential First Input Delay 680 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Remove unused JavaScript Potential savings of 708 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Initial server response time was short Root document took 80 ms
Keep the server response time for the main document short because all other requests depend on it
Minify JavaScript Potential savings of 29 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 2.5 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint 2.5 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce JavaScript execution time 2.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoids enormous network payloads Total size was 1,337 KiB
Large network payloads cost users real money and are highly correlated with long load times
Reduce the impact of third-party code Third-party code blocked the main thread for 1,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
Minimize main-thread work 3.6 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 Potential savings of 9 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
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
Avoid chaining critical requests 7 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 CPU Idle 3.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/).
Uses efficient cache policy on static assets 4 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids an excessive DOM size 200 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)

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
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
Congratulations! Your website appears to have a favicon.

aliabdaal.com Alexa Rank

53,062

Global Rank

31,418

United States

Domain Available

Domain (TDL) and Typo Status
aliabdaal.co Available Buy Now!
aliabdaal.us Available Buy Now!
aliabdaal.com Available Buy Now!
aliabdaal.org Available Buy Now!
aliabdaal.net Available Buy Now!
aiabdaal.com Available Buy Now!
qliabdaal.com Available Buy Now!
zliabdaal.com Available Buy Now!

Information Server aliabdaal.com

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
date: Tue, 13 Apr 2021 17:13:25 GMT
content-type: text/html; charset=utf-8
content-length: 7961
set-cookie: __cfduid=dd2b84da696cdd807d5dad2384b6023921618334005; expires=Thu, 13-May-21 17:13:25 GMT; path=/; domain=.aliabdaal.com; HttpOnly; SameSite=Lax
status: 304 Not Modified
x-request-id: 2686f04bf34b1277cbd866a7b6a12cb0
etag: W/"5c10-fnzu3nxnzv8ckBFoHgqV9vReS3Q"
vary: Accept-Encoding
content-encoding: gzip
age: 795
x-cache: HIT
cache-control: public, max-age=0
accept-ranges: bytes
x-request-id: 325cd952b08d2a6eea9af976988afe29
cf-cache-status: DYNAMIC
cf-request-id: 096dd25200000021515f2bd000000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
set-cookie: __cflb=02DiuCzDjsTNptQXPzsE4eZ4sKasgpcwNauU6Nhe4qhcg; SameSite=Lax; path=/; expires=Wed, 14-Apr-21 16:13:25 GMT; HttpOnly
server: cloudflare
cf-ray: 63f653300c702151-DUS
DNS Records DNS Resource Records associated with a hostname
aliabdaal.com View DNS Records

Social Data