Your Website Score is
SEO Rank : 34 Website URL: wordfun.ca Last Updated: 6 months
Success
39% of passed verification steps
Warning
38% of total warning
Errors
23% of total errors, require fast action
Share
Estimation Traffic and Earnings
80
Unique Visits
Daily
148
Pages Views
Daily
$0
Income
Daily
2,240
Unique Visits
Monthly
4,218
Pages Views
Monthly
$0
Income
Monthly
25,920
Unique Visits
Yearly
49,728
Pages Views
Yearly
$0
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 26%
Domain Authority
Domain Authority 23%
Moz Rank
2.6/10
Bounce Rate
Rate 0%
Meta Data
Title Tag
16 Characters
CROSSWORD SOLVER
Meta Description
0 Characters
NO DATA
Effective URL
22 Characters
https://www.wordfun.ca
Excerpt
Page content
Crossword Solver
Results for
Crossword Solver
I enjoy crosswords, and wrote these tools to help me. There are well over a quarter of a million words and phrases in the ...
Google Preview
Your look like this in google search result
CROSSWORD SOLVER
https://www.wordfun.ca
Crossword Solver
Results for
Crossword Solver
I enjoy crosswords, and wrote these tools to help me. There are well over a quarter of a million words and phrases in the ...
Robots.txt
File No Found
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~2.77 KB
Code Size: ~1.52 KB
Text Size: ~1.25 KB Ratio: 45.18%
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
Technologies
PWA - Manifest
Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest
Desktop
Avoids enormous network payloads
Total size was 38 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests
3 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
Max Potential First Input Delay
20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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.5 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint
0.5 s
First Contentful Paint marks the time at which the first text or image is painted
Eliminate render-blocking resources
Potential savings of 0 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 190 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
First CPU Idle
0.5 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/).
Largest Contentful Paint
0.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Minimizes main-thread work
0.1 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
Avoids an excessive DOM size
46 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)
Uses efficient cache policy on static assets
0 resources found
A long cache lifetime can speed up repeat visits to your page
Remove unused JavaScript
Potential savings of 22 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Keep request counts low and transfer sizes small
4 requests • 38 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Time to Interactive
0.5 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
Speed Index
0.5 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Mobile
Largest Contentful Paint
1.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
First Contentful Paint
1.9 s
First Contentful Paint marks the time at which the first text or image is painted
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
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
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First Meaningful Paint
1.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small
4 requests • 38 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids an excessive DOM size
46 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)
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
Tap targets are sized appropriately
100% 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
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
Minimize third-party usage
Third-party code blocked the main thread for 10 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
Uses efficient cache policy on static assets
0 resources found
A long cache lifetime can speed up repeat visits to your page
Speed Index
1.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid chaining critical requests
3 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
Initial server response time was short
Root document took 20 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint (3G)
3744 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Time to Interactive
1.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Remove unused JavaScript
Potential savings of 22 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Max Potential First Input Delay
40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First CPU Idle
1.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/).
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
Avoids enormous network payloads
Total size was 38 KiB
Large network payloads cost users real money and are highly correlated with long load times
Eliminate render-blocking resources
Potential savings of 150 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
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
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not 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
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links
View links
| First 1 Links | Relationship | HTTP Status |
| Cryptograms are now on their own page. | Internal Link | 301 |
Alexa Rank
0
Local Rank: / Users: / PageViews:4,533,853
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| wordfun.co | Available Buy Now! |
| wordfun.us | Available Buy Now! |
| wordfun.com | Already Registered |
| wordfun.org | Already Registered |
| wordfun.net | Available Buy Now! |
| wrdfun.ca | Available Buy Now! |
| zordfun.ca | Available Buy Now! |
| sordfun.ca | Available Buy Now! |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx/1.4.6 (Ubuntu)
Date: Tue, 04 Aug 2020 13:15:34 GMT
Content-Type: text/html;charset=utf-8
Connection: keep-alive
Status: 200 OK
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Powered-By: Phusion Passenger 5.1.12
Content-Encoding: gzip
Click to Add/Show Comments