Your Website Score is
SEO Rank : 19 Website URL: wplocker.pro Last Updated: 2 months
Success
70% of passed verification steps
Warning
7% of total warning
Errors
23% of total errors, require fast action
Share
Estimation Traffic and Earnings
1,843
Unique Visits
Daily
3,409
Pages Views
Daily
$6
Income
Daily
51,604
Unique Visits
Monthly
97,157
Pages Views
Monthly
$150
Income
Monthly
597,132
Unique Visits
Yearly
1,145,424
Pages Views
Yearly
$1,584
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 28%
Domain Authority
Domain Authority 7%
Moz Rank
2.8/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
58 Characters
WPLOCKER.PRO - GPL LICENSED WORDPRESS THEMES & PLUGINS
Meta Description
137 Characters
Largest collection of free gpl licensed wordpress themes and plugins available for download. Free tutorials and wordpress learning ebooks
Effective URL
20 Characters
https://wplocker.pro
Excerpt
Page content
WPLOCKER.PRO - GPL LICENSED WORDPRESS THEMES & PLUGINS
Skip to content
Menu HOMETHEMESPLUGINSLOGINRECENTLY ADDED
Instantify v3.6 – PWA & Google AMP & Facebook IA for WordPressnulled
November 22, 2020Instantify by Da...
Google Preview
Your look like this in google search result
WPLOCKER.PRO - GPL LICENSED WORDPRESS THEMES & PLUGINS
https://wplocker.pro
Largest collection of free gpl licensed wordpress themes and plugins available for download. Free tutorials and wordpress learning ebooks
Robots.txt
File Detected
Sitemap.xml
File Detected
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-10-17 / 1 year
Create on: 2019-10-17 / 1 year
Expires on: 2020-10-17 / 3 months 7 days
NameCheap, Inc ,PA
Registrar Whois Server: whois.namecheap.com
Registrar URL: www.namecheap.com
Nameservers
NS1.WPHOSTPACK.COM
NS2.WPHOSTPACK.COM
Page Size
Code & Text Ratio
Document Size: ~79.64 KB
Code Size: ~46.12 KB
Text Size: ~33.52 KB Ratio: 42.09%
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
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 CPU Idle
2.7 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
118 requests • 9,380 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Minimize third-party usage
Third-party code blocked the main thread for 230 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
Largest Contentful Paint
3.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Avoid long main-thread tasks
4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve static assets with an efficient cache policy
33 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid enormous network payloads
Total size was 9,380 KiB
Large network payloads cost users real money and are highly correlated with long load times
Initial server response time was short
Root document took 250 ms
Keep the server response time for the main document short because all other requests depend on it
Speed Index
1.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce JavaScript execution time
1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Remove unused JavaScript
Potential savings of 156 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minimize main-thread work
2.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 14.3 s
A fast page load over a cellular network ensures a good mobile user experience
Properly size images
Potential savings of 6,629 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid chaining critical requests
1 chain 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
570 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)
Cumulative Layout Shift
0.051
Cumulative Layout Shift measures the movement of visible elements within the viewport
Efficiently encode images
Potential savings of 29 KiB
Optimized images load faster and consume less cellular data
Preload key requests
Potential savings of 550 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Serve images in next-gen formats
Potential savings of 6,787 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
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
First Contentful Paint
0.7 s
First Contentful Paint marks the time at which the first text or image is painted
First Meaningful Paint
0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Estimated Input Latency
30 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
Total Blocking Time
240 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Time to Interactive
3.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
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
Max Potential First Input Delay
160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Mobile
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First CPU Idle
12.7 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 6,471 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
Serve static assets with an efficient cache policy
34 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay
630 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Document uses legible font sizes
97.16% 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
Cumulative Layout Shift
0.198
Cumulative Layout Shift measures the movement of visible elements within the viewport
Page load is not fast enough on mobile networks
Interactive at 19.0 s
A fast page load over a cellular network ensures a good mobile user experience
Remove unused JavaScript
Potential savings of 157 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Defer offscreen images
Potential savings of 5,164 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index
7.3 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
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
Keep request counts low and transfer sizes small
146 requests • 9,397 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Initial server response time was short
Root document took 170 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint
7.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids an excessive DOM size
568 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
Reduce JavaScript execution time
9.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
First Contentful Paint
2.2 s
First Contentful Paint marks the time at which the first text or image is painted
First Contentful Paint (3G)
4486.151290893555 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Properly size images
Potential savings of 3,731 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid enormous network payloads
Total size was 9,397 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Total Blocking Time
3,600 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Estimated Input Latency
310 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
First Meaningful Paint
2.2 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid chaining critical requests
1 chain 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
Time to Interactive
19.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Minimize main-thread work
14.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Reduce the impact of third-party code
Third-party code blocked the main thread for 3,530 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
Preload key requests
Potential savings of 3,480 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
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
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
1,557
Local Rank: RS / Users: 6.4% / PageViews: 73.1%62,887
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| wplocker.co | Already Registered |
| wplocker.us | Already Registered |
| wplocker.com | Already Registered |
| wplocker.org | Already Registered |
| wplocker.net | Already Registered |
| wlocker.pro | Already Registered |
| zplocker.pro | Already Registered |
| splocker.pro | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Sun, 22 Nov 2020 22:21:29 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d985d383afc6f40f6bc8dfc95834dcae41606083689; expires=Tue, 22-Dec-20 22:21:29 GMT; path=/; domain=.wplocker.pro; HttpOnly; SameSite=Lax
x-ua-compatible: IE=edge
link: ; rel="https://api.w.org/"
cache-control: private, proxy-revalidate, s-maxage=0
link: ; rel=preload; as=style,; rel=preload; as=script,; rel=preload; as=script,; rel=preload; as=script,; rel=preload; as=script,; rel=preload; as=script,; rel=preload; as=script,; rel=preload; as=script
vary: Accept-Encoding
x-turbo-charged-by: LiteSpeed
x-litespeed-cache: hit
cf-cache-status: DYNAMIC
cf-request-id: 0693a5537a000099536c1bb000000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=EbDIs4QjWq5wwMHWxqnnDmJ3x3na11gxoM1tbok51GbfdWiqk9jcpO8%2BOYYrHABSPGVzdnKTjntn%2Fp1XMtagRZZfCW2GsNSrWMW6oEw%3D"}],"group":"cf-nel","max_age":604800}
nel: {"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 5f660b32589d9953-LAX
content-encoding: gzip
Click to Add/Show Comments