Your Website Score is
SEO Rank : 50 Website URL: scanwp.net Last Updated: 2 months

Success
55% of passed verification steps
Warning
30% of total warning
Errors
15% of total errors, require fast action
Share
Estimation Traffic and Earnings
0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 43%
Domain Authority
Domain Authority 28%
Moz Rank
4.3/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
66 Characters
SCAN WP | WORDPRESS THEME DETECTOR | PLUGIN DETECTOR | WP DETECTOR
Meta Description
154 Characters
What Wordpress theme is that? What plugin is that? I wonder what WP theme is being used. Sound familiar? Just use Scan WP and detect any theme and plugin.
Effective URL
18 Characters
https://scanwp.net
Excerpt
Page content
Scan WP | Wordpress Theme Detector | Plugin Detector | WP Detector
...
Google Preview
Your look like this in google search result
SCAN WP | WORDPRESS THEME DETECTOR | PLUGIN DETECTOR | WP DE
https://scanwp.net
What Wordpress theme is that? What plugin is that? I wonder what WP theme is being used. Sound familiar? Just use Scan WP and detect any theme and plu
Robots.txt
File Detected
Sitemap.xml
File No Found
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: 2019-05-05 / 2 years
Create on: 2015-06-04 / 6 years
Expires on: 2020-06-04 / 10 months 22 days
NameCheap, Inc. ,
Registrar Whois Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Nameservers
LUCY.NS.CLOUDFLARE.COM
PABLO.NS.CLOUDFLARE.COM
Page Size
Code & Text Ratio
Document Size: ~69.74 KB
Code Size: ~68.11 KB
Text Size: ~1.63 KB Ratio: 2.34%
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

The web app manifest is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in areas where they would expect to see apps (for example, a mobile device's home screen)
Param name
App
Manifest is not valid
Your manifest are missing some important params, read more in Web App Manifest
Desktop
Defer offscreen images
Potential savings of 12 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Remove unused CSS
Potential savings of 56 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
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
Largest Contentful Paint
1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Time to Interactive
2.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
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
Avoids enormous network payloads
Total size was 1,554 KiB
Large network payloads cost users real money and are highly correlated with long load times
Eliminate render-blocking resources
Potential savings of 350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
10 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 332 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
Speed Index
0.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Max Potential First Input Delay
60 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 7 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
Serve images in next-gen formats
Potential savings of 134 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
First Contentful Paint
0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Keep request counts low and transfer sizes small
63 requests • 1,554 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First CPU Idle
2.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 an excessive DOM size
649 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)
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
Initial server response time was short
Root document took 330 ms
Keep the server response time for the main document short because all other requests depend on it
First Meaningful Paint
0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Cumulative Layout Shift
0.048
Cumulative Layout Shift measures the movement of visible elements within the viewport
Uses efficient cache policy on static assets
6 resources found
A long cache lifetime can speed up repeat visits to your page
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
Includes front-end JavaScript libraries with known security vulnerabilities
9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Preload key requests
Potential savings of 190 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Mobile
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
Minimize main-thread work
2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index
2.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoids an excessive DOM size
649 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 JavaScript
Potential savings of 332 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Remove unused CSS
Potential savings of 56 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
First Contentful Paint
2.3 s
First Contentful Paint marks the time at which the first text or image is painted
Time to Interactive
9.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Uses efficient cache policy on static assets
6 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint
3.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
First CPU Idle
8.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/).
Keep request counts low and transfer sizes small
60 requests • 1,514 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Defer offscreen images
Potential savings of 12 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Minimize third-party usage
Third-party code blocked the main thread for 200 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
Eliminate render-blocking resources
Potential savings of 1,280 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Total Blocking Time
430 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids enormous network payloads
Total size was 1,514 KiB
Large network payloads cost users real money and are highly correlated with long load times
Cumulative Layout Shift
0.18
Cumulative Layout Shift measures the movement of visible elements within the viewport
Preload key requests
Potential savings of 1,080 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
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
Tap targets are not sized appropriately
83% 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
Avoid serving legacy JavaScript to modern browsers
Potential savings of 7 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
Estimated Input Latency
70 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
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
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
Max Potential First Input Delay
290 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Serve images in next-gen formats
Potential savings of 120 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
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
Includes front-end JavaScript libraries with known security vulnerabilities
9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
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 Meaningful Paint
2.3 s
First Meaningful Paint measures when the primary content of a page is visible
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
Warning! Your title is not optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site 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
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 |
Best SEO and PPC Tool - Extended Free Trial | Internal Link | 301 |
Save as Bookmark | Internal Link | 200 |
Share on Linkedin | Internal Link | 400 |
Share on Twitter | Internal Link | 400 |
Share on Facebook | Internal Link | 302 |
http://scanwp.net/ | Internal Link | 301 |
Find a Theme | Internal Link | 200 |
Find a Plugin | Internal Link | 200 |
Shared Hosting | Internal Link | 200 |
WordPress Hosting | Internal Link | 200 |
VPS Hosting | Internal Link | 200 |
Cloud Hosting | Internal Link | 200 |
Blog | Internal Link | 200 |
Wordpress Tutorials | Internal Link | 200 |
WordPress Plugins | Internal Link | 200 |
WordPress Themes | Internal Link | 200 |
FAQ | Internal Link | 200 |
Top 50 Plugins | Internal Link | 301 |
Top 50 Themes | Internal Link | 301 |
Elegant Themes | Internal Link | 301 |
Alexa Rank
0
Local Rank: / Users: / PageViews:
Global Rank
Domain Available
Domain (TDL) and Typo | Status |
---|---|
scanwp.co | Already Registered |
scanwp.us | Already Registered |
scanwp.com | Already Registered |
scanwp.org | Already Registered |
scanwp.net | Already Registered |
sanwp.net | Already Registered |
wcanwp.net | Already Registered |
xcanwp.net | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Thu, 25 Feb 2021 00:00:23 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d4c3bee438dd2a24df3ac1ab7f7a59a841614211223; expires=Sat, 27-Mar-21 00:00:23 GMT; path=/; domain=.scanwp.net; HttpOnly; SameSite=Lax; Secure
vary: Accept-Encoding
access-control-allow-origin: *
access-control-allow-headers: Origin, Content-Type
cache-control: private, must-revalidate
pragma: no-cache
expires: -1
set-cookie: XSRF-TOKEN=eyJpdiI6IlJEZkZEZ25HQ3dBZUplVUJ0MlwvNFBnPT0iLCJ2YWx1ZSI6IklVRFoyR3k4ZEJFVndJU1lmZjZneVlOSCtTZ3V0cVNsRHI1UEtoQ1JqMUxBR1RIaktvWVJUV0I1VkdJdjBlck8iLCJtYWMiOiIyOWJlMWRmNDhkNWY5ZDlhYTU3MTBiNGE3NjU4YThhZDRkZmM4MWMzZGQ0NDBmMDkzZDZhZGJjY2JjNWI5Y2ExIn0%3D; expires=Thu, 25-Feb-2021 02:00:23 GMT; Max-Age=7200; path=/
cf-cache-status: DYNAMIC
set-cookie: laravel_session=eyJpdiI6IjJ3K1crQmN1RmNLSEpuS21CZHIyaUE9PSIsInZhbHVlIjoicnFOU0QrTVRPNlc2S0VCcUJcLzFKaExlcytic1FkMk9aejJYR0VHR2pldXpcL2NlTEZrZVprMjdlNDgrNjBHdEpvIiwibWFjIjoiZjY5ZjA5NzA2MTM3YjdhZTk3YTNkZTlhNWZmMDM0ZDA5YTlkZDE4NGQ3OWMzN2M5ZDRhNGZlMDdlYTBhNDM3YyJ9; expires=Thu, 25-Feb-2021 02:00:23 GMT; Max-Age=7200; path=/; httponly
cf-request-id: 087815a7d900003630e62aa000000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
report-to: {"max_age":604800,"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=jwkKLVWoaewWcPGZVeJRFuU%2Bs7RxSPIynGU6vueA4eo12kdk0eakYhnJ1wt5fZoFEq9KyymqxxDJLOWzaghRFgUe1HfgcHJO6Toe"}],"group":"cf-nel"}
nel: {"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 626d2552fc723630-LAX
content-encoding: gzip
Click to Add/Show Comments