Donmai.us - SEO Checker - Website Review

Your Website Score is

Similar Ranking

MARKETING EYE BRISBANE | NEXT LEVEL MARKETING AGENCY

marketingeyebrisbane.com.au

LAYER CHICKEN CAGE

poultrymachine.com

FILERIO : : CLOUD FILE STORAGE - EASY WAY TO SHARE YOUR FILES

filerio.in

GROW YOUR BUSINESS WITH CONTESTS & SOCIAL MARKETING APPS

gleam.io

TERCEIRO Z - HENTAI, INCESTO, ---Ô, QUADRINHOS ERÓTICOS E MUITO MAIS!

terceiroz.com

ERROR: THE REQUESTED URL COULD NOT BE RETRIEVED

qhnky.com

METASRC PATCH 9.24 HOME - 5V5

metasrc.com

Latest Sites

OSLOWAY | YOUR BEST LOCAL TOURS AND EXPERIENCES IN OSLO

osloway.no

JUST A MOMENT...

hourlyminer.com

ピアノ教室ネット｜先生との出会いはここから。全国のピアノ教室から検索！

pnet.kawai.jp

ADAGIETTOピアノ教室|飯能|ピアノに興味がある皆さんへ|

adagiettopiano.com

ГЛАВНАЯ | UNIEX

uniex.biz

AHMADIMADO - TRUSTED DOGECOIN CLOUD MINING

ahmadimado.net

DOGESILVA LIMITED - HOME

dogesilva.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

19 donmai.us Last Updated: 8 months

Success 62% of passed verification steps

Warning 15% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 98%

Best Practices Desktop Score 92%

SEO Desktop Score 100%

Progressive Web App Desktop Score 54%

Performance Mobile Score 66%

Best Practices Mobile Score 85%

SEO Mobile Score 94%

Progressive Web App Mobile Score 56%

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

DANBOORU

Meta Description 24 Characters

Find good --- art fast

Effective URL 26 Characters

https://danbooru.donmai.us

Excerpt Page content

Danbooru Danbooru Login Posts Comments Notes Artists Tags Poo...

Keywords Cloud Density

tags3 search3 help3 danbooru2 pokemon2 order2 breasts2 fate2 posts2 yuri1

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
tags	3
search	3
help	3
danbooru	2
pokemon	2
order	2
breasts	2
fate	2
posts	2
yuri	1

Google Preview Your look like this in google search result

DANBOORU

https://danbooru.donmai.us

Find good --- art fast

Robots.txt File Detected

http://donmai.us/robots.txt

Sitemap.xml File Detected

http://donmai.us/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~76.09 KB

Code Size: ~74.78 KB

Text Size: ~1.31 KB Ratio: 1.72%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Desktop

Serve static assets with an efficient cache policy 29 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 100 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 1.0 s

Time to interactive is the amount of time it takes for the page to become fully interactive

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

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

User Timing marks and measures 1 user timing

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Server response times are low (TTFB) Root document took 350 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 220 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

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

Total Blocking Time 30 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

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

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

Speed Index 0.9 s

Speed Index shows how quickly the contents of a page are visibly populated

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).

Avoids enormous network payloads Total size was 632 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimizes main-thread work 0.6 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.9 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 5 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

Avoids an excessive DOM size 419 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)

First Meaningful Paint 0.9 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 37 requests • 632 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Mobile

Avoids enormous network payloads Total size was 665 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 2.2 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 3.8 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 4 chains found

Avoids an excessive DOM size 419 elements

Preload key requests Potential savings of 1,290 ms

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

First Meaningful Paint 3.8 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 37 requests • 665 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 29 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 450 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 6.1 s

Time to interactive is the amount of time it takes for the page to become fully interactive

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) 7502 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Estimated Input Latency 100 ms

Tap targets are not sized appropriately 35% 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

Document uses legible font sizes 92.56% 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 1 user timing

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Server response times are low (TTFB) Root document took 250 ms

Time To First Byte identifies the time at which your server sends a response

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

Reduce the impact of third-party code Third-party code blocked the main thread for 460 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

Total Blocking Time 680 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 1.4 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

Defer offscreen images Potential savings of 21 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Speed Index 4.1 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 5.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).

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Date: Wed, 18 Dec 2019 22:45:05 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Set-Cookie: __cfduid=d0d9e069e85a8cef869e8cd1127fd38c01576709104; expires=Fri, 17-Jan-20 22:45:04 GMT; path=/; domain=.donmai.us; HttpOnly; SameSite=Lax
Vary: Accept-Encoding
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Permitted-Cross-Domain-Policies: none
Referrer-Policy: strict-origin-when-cross-origin
Access-Control-Allow-Origin: *
Cache-Control: max-age=0, private, must-revalidate
Set-Cookie: _danbooru2_session=mP0TtFEfjphU872Gpdgla%2FNuChhJ4OMftmH%2BZ7%2FYImarGnl5fB8As2uBJ3mEiiH%2BTr8xiPcFqkjXDJ0vm1nnGW3UmCYGdCcgG7udW8gK7Bod301xSrUkQ3P%2Fz4hamPtZUOCaFUfBSggN8%2Fqo3GnBiPBF1Tp%2F5hTY1Qq%2F4VLxWcwFmW%2BBDSr31OhKxFNnkKBJOlqL07hvX%2FLdGcOGGwoxDksfTdmuXAa7oY8d%2BkWiMejSw%2FVtkjoIsYepOGJpqgvTjl4hoC%2BcMjkcOo7IbcOiHIxlF1sJbv38z%2BOYdy%2FZvS%2FSn516cw%2BJI75CgkKfieG2BWL66yWXjZN5YeuTHSTh5wrxaySPc9xFSX1TF1kendO6uF1yChfzeh5NrCfOBCZp3Is63Q%3D%3D--ZNnsboVos%2FCWx%2BHe--Dzj7LwTsaT2u1wBRBp7ELQ%3D%3D; domain=.donmai.us; path=/; expires=Sun, 18 Dec 2039 22:45:04 -0000; secure; HttpOnly; SameSite=Lax
X-Request-Id: 745915d1-8871-40db-ad8f-eccf54d9f82b
X-Runtime: 0.046130
Strict-Transport-Security: max-age=31556952; preload
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Alt-Svc: h3-24=":443"; ma=86400, h3-23=":443"; ma=86400
Server: cloudflare
CF-RAY: 5474aa41ab009222-EWR
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	donmai.us	172.64.139.30	IN	299
A	donmai.us	172.64.138.30	IN	299
NS	donmai.us	alec.ns.cloudflare.com	IN	68644
NS	donmai.us	adel.ns.cloudflare.com	IN	68644
TXT	donmai.us	v=spf1 -all	IN	300
TXT	donmai.us	ca3-8a6a219fe2e54e878a3d351e281a56a6	IN	300
TXT	donmai.us	google-site-verification=VNLiS2VLxjYQKbuupFjE_Z55bGaJmQlXCNYTR89VvyM	IN	300
AAAA	donmai.us	2606:4700:e2::ac40:8b1e	IN	300
AAAA	donmai.us	2606:4700:e2::ac40:8a1e	IN	300