substack.com score is

Similar Ranking
58
MOST ACCURATE PRAYER TIMES, QURAN, ATHAN AND QIBLA DIRECTION | ISLAMICFINDER
islamicfinder.org
58
SUBSTACK
substack.com
58
DEV COMMUNITY ????‍????????‍????
dev.to
58
BILLIGE FLÜGE, HOTELS & MIETWAGEN VERGLEICHEN | SKYSCANNER
skyscanner.com
58
PADDLE - REVENUE DELIVERY PLATFORM FOR SAAS
paddle.com
58
FREELANCER MERKEZI - WEBLY
webly.com.tr
58
JOB SEARCH, COMPANIES HIRING NEAR ME, AND ADVICE | THE MUSE
themuse.com
Latest Sites
19
ÖĞRENCI MERKEZI » KYK BURS BAŞVURULARI ÖDÜLLÜ YARIŞMALAR
ogrencimerkezi.org
19
ESKIŞEHIR İLAÇLAMA FIRMALARI | ESKIŞEHIR BÖCEK İLAÇLAMA
biyoes.com.tr
12
RUHSAL BEDENSEL – TIP SAĞLIK DÜNYASI - RUHSAL BEDENSEL
ruhsalbedensel.com
29
MUHASEBE FORUM : MUHASEBE VE MEVZUAT FORUM SITESI | MUHASEBE FORUM
muhasebeforum.com.tr
3
QUVETOPEDIA
quvetopedia.com
5
AYMINA HOME | HAMILE YASTIĞI VUCUDUN 5 FARKLI BOLGESINE EŞ ZAMANLI OLARAK DESTEK VE RAHATLAMA SAĞLAR. HAMILELIK DONEMINDE ANNE ADAYLARIMIZIN SAĞLIĞINI KORUYARAK HAMILELIK SÜRECININ RAHAT GEÇMESINE YAR
ayminahome.com
16
CMC REKLAM VE MIMARLIK
cmcreklam.com.tr
Top Technologies
PHP
Programming Languages
CloudFlare
CDN
Google Font API
Font Scripts
WordPress
CMS
jQuery
JavaScript Frameworks
Nginx
Web Servers
Font Awesome
Font Scripts
Apache
Web Servers
Twitter Bootstrap
Web Frameworks
Google Tag Manager
Tag Managers

58 substack.com Last Updated: 3 years

Success 78% of passed verification steps
Warning 7% of total warning
Errors 15% of total errors, require fast action
Share

Desktop Speed Score

Mobile Speed Score

Performance Desktop Score 99%
Best Practices Desktop Score 100%
SEO Desktop Score 92%
Progressive Web App Desktop Score 45%
Performance Mobile Score 89%
Best Practices Mobile Score 100%
SEO Mobile Score 90%
Progressive Web App Mobile Score 50%
Page Authority Authority 59%
Domain Authority Domain Authority 77%
Moz Rank 5.9/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 8 Characters
SUBSTACK
Meta Description 103 Characters
Substack makes it simple for a writer to start an email newsletter that makes money from subscriptions.
Effective URL 20 Characters
https://substack.com
Excerpt Page content
Substack WritersStart a publicationSwitch to SubstackWhy go paid?ResourcesEventsAbout usAboutJobsBlogHelpSign inTake back your mindSubstack is a place for independent writing. Subscribe directly to writers you trust.Start readingWrite on SubstackPublicationsData: Made Not Found (by danah)by danah boyd · Launched 2 months agoAssorted research thoughts on sociotechnical topics ranging from the census to algorithmic accountability, all with an eye to how data and society intersect with structural inequityBad Guruby Alex Ebert · Launched 4 months agoThe essays, stories, and poems of Alex Ebert ...
Keywords Cloud Density
launched6 substack5 months5 about4 writers3 help3 danah2 privacy2 heath2 alex2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
launched 6
substack 5
months 5
about 4
writers 3
help 3
danah 2
privacy 2
heath 2
alex 2
Google Preview Your look like this in google search result
SUBSTACK
https://substack.com
Substack makes it simple for a writer to start an email newsletter that makes money from subscriptions.
Robots.txt File Detected
http://substack.com/robots.txt
Sitemap.xml File Detected
http://substack.com/sitemap.xml
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 2020-03-23 / 4 years
Create on: 2010-04-27 / 14 years
Expires on: 2021-04-27 / 36 months 13 days

Amazon Registrar, Inc. ,
Registrar Whois Server: whois.registrar.amazon.com
Registrar URL: http://registrar.amazon.com

Nameservers
NS-1070.AWSDNS-05.ORG
NS-1948.AWSDNS-51.CO.UK
NS-212.AWSDNS-26.COM
NS-711.AWSDNS-24.NET
Page Size Code & Text Ratio
Document Size: ~82.24 KB
Code Size: ~14.23 KB
Text Size: ~68.01 KB Ratio: 82.70%

substack.com Estimation Traffic and Earnings

51,789
Unique Visits
Daily
95,809
Pages Views
Daily
$93
Income
Daily
1,450,092
Unique Visits
Monthly
2,730,557
Pages Views
Monthly
$2,325
Income
Monthly
16,779,636
Unique Visits
Yearly
32,191,824
Pages Views
Yearly
$24,552
Income
Yearly

Web Technologies

PWA - Manifest

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

Desktop Speed Score

Desktop Screenshot
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
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
Minimizes main-thread work 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
Remove unused JavaScript Potential savings of 232 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Eliminate render-blocking resources Potential savings of 290 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Remove unused CSS Potential savings of 72 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
Minify CSS Potential savings of 10 KiB
Minifying CSS files can reduce network payload sizes
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 23 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
First Meaningful Paint 0.7 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 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
Speed Index 0.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Properly size images Potential savings of 89 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted
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
Uses efficient cache policy on static assets 1 resource found
A long cache lifetime can speed up repeat visits to your page
Total Blocking Time 50 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
Initial server response time was short Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids enormous network payloads Total size was 510 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint 0.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids an excessive DOM size 188 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)
Time to Interactive 1.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Keep request counts low and transfer sizes small 15 requests • 510 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First CPU Idle 1.0 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/).
Serve images in next-gen formats Potential savings of 14 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
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

Mobile Speed Score

Mobile Screenshot
Max Potential First Input Delay 420 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids an excessive DOM size 179 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.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Remove unused CSS Potential savings of 72 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
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 410 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused JavaScript Potential savings of 232 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Properly size images Potential savings of 67 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Document uses legible font sizes 99.78% 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
Initial server response time was short Root document took 90 ms
Keep the server response time for the main document short because all other requests depend on it
First Meaningful Paint 2.0 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint 2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
First Contentful Paint (3G) 3960 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,140 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First CPU Idle 4.4 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/).
Avoids enormous network payloads Total size was 510 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 23 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
Uses efficient cache policy on static assets 1 resource found
A long cache lifetime can speed up repeat visits to your page
Keep request counts low and transfer sizes small 15 requests • 510 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Minimizes main-thread work 1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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 images in next-gen formats Potential savings of 14 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Time to Interactive 4.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Minify CSS Potential savings of 10 KiB
Minifying CSS files can reduce network payload sizes
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
First Contentful Paint 2.0 s
First Contentful Paint marks the time at which the first text or image is painted
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
Speed Index 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Tap targets are not sized appropriately 67% 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 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
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.
Broken Links
Congratulations! You not have broken links View links
First 20 Links Relationship HTTP Status
http://substack.com/home Internal Link 301
Start a publication Internal Link 200
Switch to Substack Internal Link 301
Why go paid? Internal Link 301
Resources Internal Link 301
Events Internal Link 301
About Internal Link 301
Jobs Internal Link 301
Blog Internal Link 200
Help Internal Link 200
Write on Substack Internal Link 301
Data: Made Not Found (by danah)by danah boyd · Launched 2 months agoAssorted research thoughts on sociotechnical topics ranging from the census to algorithmic accountability, all with an eye to how data and society intersect with structural inequity Internal Link 200
https://zephoria.substack.com Internal Link 200
Bad Guruby Alex Ebert · Launched 4 months agoThe essays, stories, and poems of Alex Ebert (and A.E. Turnpike and Edward Sharpe, too) and guests. Internal Link 200
https://badguru.substack.com Internal Link 200
Maps for the Getawayby Tom Fish · Launched 4 months agoDeep dives into geography, technology, politics, and culture Internal Link 200
https://fish.substack.com Internal Link 200
How Not to F*ck Up Your Faceby Valerie Monroe · Launched 2 months agophilosophical and practical advice for anyone who's ever looked into a mirror Internal Link 200
https://valeriemonroe.substack.com Internal Link 200
Afterglow by Glenn Heath Jr. · Launched a year agoA weekly film newsletter written by Glenn Heath Jr. Internal Link 200

substack.com Alexa Rank

1,829

Global Rank

660

United States

Domain Available

Domain (TDL) and Typo Status
substack.co Available Buy Now!
substack.us Available Buy Now!
substack.com Available Buy Now!
substack.org Available Buy Now!
substack.net Available Buy Now!
sbstack.com Available Buy Now!
wubstack.com Available Buy Now!
xubstack.com Available Buy Now!

Information Server substack.com

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/2 200 
date: Sun, 28 Mar 2021 15:49:44 GMT
content-type: text/html; charset=utf-8
set-cookie: __cfduid=d42dd458216e593c0689b6b45393bb3311616946584; expires=Tue, 27-Apr-21 15:49:44 GMT; path=/; domain=.substack.com; HttpOnly; SameSite=Lax
cf-ray: 6372029b7ddefafa-DUS
age: 0
cache-control: no-cache
etag: W/"148ed-tHgQZ8F/qWLOBLab+LQosDU2JHM"
strict-transport-security: max-age=31536000
vary: Accept-Encoding
via: 1.1 vegur
cf-cache-status: HIT
cf-request-id: 091b1ff5280000fafaa1313000000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
x-cluster: substack
x-frame-options: sameorigin
x-powered-by: Express
x-served-by: Substack
server: cloudflare
content-encoding: gzip
DNS Records DNS Resource Records associated with a hostname
substack.com View DNS Records
Type Name Value Class TTL
A substack.com 104.18.1.201 IN 231
A substack.com 104.18.0.201 IN 231
NS substack.com ali.ns.cloudflare.com IN 86400
NS substack.com lee.ns.cloudflare.com IN 86400
MX substack.com mxb.mailgun.org IN 300
MX substack.com mxa.mailgun.org IN 300
TXT substack.com google-site-verification=DAkdykID6WqQM6tT7IfSu9_uB7-qIdB039MA_C3T3eA IN 300
TXT substack.com v=spf1 include:_spf.google.com include:mailgun.org include:mail.zendesk.com ~all IN 300
TXT substack.com google-site-verification=vQEKLOUDfKNOQAv9W3EUMiRD6e5ibAEPhc2yCzP7big IN 300
AAAA substack.com IN 231
AAAA substack.com IN 231

Social Data

Delicious Total: 0
Facebook Total: 0
Google Total: 0
Linkedin Total: 0
Pinterest Total: 0
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

About Us

Contact Info

OTTOROYAL INC

Follow Us

Twitter
Copyright 2021
Languages | English