Your Website Score is

Similar Ranking

14
PROTECTIVE HOMOEOPATHY
protectivehomoeopathy.blogspot.com
14
AVA AUGUST
avaaugust.com
14
AUSTINE NORTH | OFFICIAL WEBSITE
austinenorth.art
14
ZEBIQ TECHNOLOGY - ZEBIQ TECHNOLOGY
zebiqtechnology.com
14
BEATS & SMILES
midlandsdj.com
14
BOT VERIFICATION
uniqueradio.org

Latest Sites

99
YOUTUBE
m.youtube.com
2
JUST A MOMENT...
deepseek.com
2
YOUTUBE
youtu.be
14
LIGHTWORKER SERVICES 2-0 – ASPIRING TO INSPIRE HUMANITY
lws2-0.org

Top Technologies

Google Font API
Font Scripts
Nginx
Web Servers
CloudFlare
CDN
Varnish
Cache Tools
Google Tag Manager
Tag Managers
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks
WordPress
CMS

14 dandwiki.com Last Updated: 2 days

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

Desktop

Mobile

Performance Desktop Score 97%
Best Practices Desktop Score 96%
SEO Desktop Score 92%
Performance Mobile Score 68%
Best Practices Mobile Score 93%
SEO Mobile Score 92%
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 12 Characters
D&D WIKI
Meta Description 0 Characters
NO DATA
Effective URL 29 Characters
https://www.dandwiki.com/wiki
Excerpt Page content
D&D Wiki Main Page From D&D Wiki Jump to navigation Jump to search Welcome To D&D Wiki! Dungeons and Dragons Wiki pages 5th Edition (5e) Homebrew Content New classes,...
Keywords Cloud Density
wiki15 pages15 homebrew14 items14 page10 content10 published9 help7 deities6 classes6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
wiki 15
pages 15
homebrew 14
items 14
page 10
content 10
published 9
help 7
deities 6
classes 6
Google Preview Your look like this in google search result
D&D WIKI
https://www.dandwiki.com/wiki
D&D Wiki Main Page From D&D Wiki Jump to navigation Jump to search Welcome To D&D Wiki! Dungeons and Dragons Wiki pages 5th Edition (5e) Homebrew Content New classes,...
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~31.36 KB
Code Size: ~23.36 KB
Text Size: ~8 KB Ratio: 25.52%

Social Data

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

Desktop

Desktop Screenshot
Properly size images Est savings of 12 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid chaining critical requests 2 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
Reduce unused JavaScript Est savings of 330 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Serve static assets with an efficient cache policy 12 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint 1.2 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 60 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
Legacy JavaScript Est savings of 28 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support legacy browsers
Improve image delivery Est savings of 14 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
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
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
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Use efficient cache lifetimes Est savings of 724 KiB
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 2.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Total Blocking Time 40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid serving legacy JavaScript to modern browsers Est savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Avoids enormous network payloads Total size was 1,460 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Initial server response time was short Root document took 270 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce unused CSS Est savings of 35 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First Contentful Paint 0.3 s
First Contentful Paint marks the time at which the first text or image is painted
Eliminate render-blocking resources Est savings of 60 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
Server Backend Latencies 10 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
Avoids an excessive DOM size 436 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)
Serve images in next-gen formats Est savings of 291 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Mobile

Mobile Screenshot
JavaScript execution time 1.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Legacy JavaScript Est savings of 28 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support legacy browsers
Cumulative Layout Shift 0.051
Cumulative Layout Shift measures the movement of visible elements within the viewport
Improve image delivery Est savings of 22 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Reduce unused JavaScript Est savings of 345 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoids enormous network payloads Total size was 1,462 KiB
Large network payloads cost users real money and are highly correlated with long load times
Server Backend Latencies 10 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
Avoid large layout shifts 3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
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
Serve static assets with an efficient cache policy 12 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint 1.6 s
First Contentful Paint marks the time at which the first text or image is painted
Max Potential First Input Delay 130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Properly size images Est savings of 7 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Total Blocking Time 210 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 4.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Minimize main-thread work 2.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Avoid serving legacy JavaScript to modern browsers Est savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Avoid chaining critical requests 2 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
Use efficient cache lifetimes Est savings of 727 KiB
A long cache lifetime can speed up repeat visits to your page
Avoid long main-thread tasks 8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve images in next-gen formats Est savings of 291 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Document uses legible font sizes 69.02% 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
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
Avoids an excessive DOM size 433 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 Est savings of 35 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Time to Interactive 10.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Eliminate render-blocking resources Est savings of 200 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Initial server response time was short Root document took 260 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint 10.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted

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
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
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

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
dandwiki.co Available
dandwiki.us Available
dandwiki.com Already Registered
dandwiki.org Already Registered
dandwiki.net Already Registered
dndwiki.com Already Registered
eandwiki.com Available
candwiki.com Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Sat, 31 May 2025 20:33:38 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Server: cloudflare
X-Content-Type-Options: nosniff
Vary: Accept-Encoding,Cookie
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Cache-Control: private, must-revalidate, max-age=0
Content-Language: en
X-Request-Id: 7d361ca7f5feda2f488582a0
Last-Modified: Sat, 31 May 2025 20:33:38 GMT
X-Cache: MISS from c1OMF24I0p232A
X-Cache-Lookup: MISS from c1OMF24I0p232A:80
Via: 1.1 c1OMF24I0p232A (squid/4.10)
Cf-Cache-Status: DYNAMIC
Report-To: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=k3QcyPI%2FHwTShdo9b5o5LMpF%2FQKiSyaPzDogrG7SPMQLzcgLFSlsqil2rx%2B5Fs9hIpNTOkvbiEM2XQ9aDa4IhAn9u5aV0hbpv22KhT3o"}]}
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Content-Encoding: gzip
CF-RAY: 94893f578856ac26-YYZ
alt-svc: h3=":443"; ma=86400
DNS Records DNS Resource Records associated with a hostname
View DNS Records