Your Website Score is
SEO Rank : 11 Website URL: linkrex.net Last Updated: 5 months
Success
63% of passed verification steps
Warning
7% of total warning
Errors
30% of total errors, require fast action
Share
Estimation Traffic and Earnings
954
Unique Visits
Daily
1,764
Pages Views
Daily
$4
Income
Daily
26,712
Unique Visits
Monthly
50,274
Pages Views
Monthly
$100
Income
Monthly
309,096
Unique Visits
Yearly
592,704
Pages Views
Yearly
$1,056
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 39%
Domain Authority
Domain Authority 37%
Moz Rank
3.9/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
49 Characters
LINKREX.NET - EARN MONEY BY SHARING SHORT LINKS!
Meta Description
125 Characters
Earn money for each visitor to your shortened links with linkrex.net! Earn up to $150 daily by sharing links on the internet.
Effective URL
19 Characters
https://linkrex.net
Excerpt
Page content
Linkrex.net - Earn Money By Sharing Short Links!
Home
Publisher Rates
Advertising
Pro
Login
Register
Shorten, Share & Earn MoneyLinkrex is one of the trusted &...
Meta Keywords
9 Detected
Google Preview
Your look like this in google search result
LINKREX.NET - EARN MONEY BY SHARING SHORT LINKS!
https://linkrex.net
Earn money for each visitor to your shortened links with linkrex.net! Earn up to $150 daily by sharing links on the internet.
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-01-08 / 2 years
Create on: 2017-11-18 / 3 years
Expires on: 2020-11-18 / 3 months 10 days
GoDaddy.com, LLC ,
Registrar Whois Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Nameservers
LARS.NS.CLOUDFLARE.COM
VENUS.NS.CLOUDFLARE.COM
Page Size
Code & Text Ratio
Document Size: ~24.58 KB
Code Size: ~16.97 KB
Text Size: ~7.61 KB Ratio: 30.97%
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 gcm sender id
376695005133
Manifest is not valid
Your manifest are missing some important params, read more in Web App Manifest
Desktop
Avoid long main-thread tasks
5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
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 serving legacy JavaScript to modern browsers
Potential savings of 0 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 60 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
1.1 s
First Contentful Paint marks the time at which the first text or image is painted
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
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 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
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
Serve static assets with an efficient cache policy
19 resources found
A long cache lifetime can speed up repeat visits to your page
Keep request counts low and transfer sizes small
47 requests • 769 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Cumulative Layout Shift
0.005
Cumulative Layout Shift measures the movement of visible elements within the viewport
Eliminate render-blocking resources
Potential savings of 990 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Defer offscreen images
Potential savings of 25 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoids an excessive DOM size
353 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 chaining critical requests
23 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 initial server response time
Root document took 4,900 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 20 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
Minify CSS
Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
Avoids enormous network payloads
Total size was 769 KiB
Large network payloads cost users real money and are highly correlated with long load times
Remove unused JavaScript
Potential savings of 230 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
JavaScript execution time
0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Remove unused CSS
Potential savings of 32 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
60 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
Largest Contentful Paint
1.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
First CPU Idle
1.1 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/).
First Meaningful Paint
1.1 s
First Meaningful Paint measures when the primary content of a page is visible
Preload key requests
Potential savings of 290 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Total Blocking Time
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Time to Interactive
1.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Speed Index
5.5 s
Speed Index shows how quickly the contents of a page are visibly populated
User Timing marks and measures
3 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Properly size images
Potential savings of 64 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content
Mobile
Serve static assets with an efficient cache policy
19 resources found
A long cache lifetime can speed up repeat visits to your page
Initial server response time was short
Root document took 340 ms
Keep the server response time for the main document short because all other requests depend on it
Defer offscreen images
Potential savings of 60 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 30 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
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
Total Blocking Time
190 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First CPU Idle
6.2 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/).
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content
Speed Index
5.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Cumulative Layout Shift
0.097
Cumulative Layout Shift measures the movement of visible elements within the viewport
Tap targets are not sized appropriately
90% 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
Keep request counts low and transfer sizes small
47 requests • 743 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Contentful Paint (3G)
7845 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
First Contentful Paint
3.9 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid large layout shifts
1 element found
These DOM elements contribute most to the CLS of the page.
First Meaningful Paint
3.9 s
First Meaningful Paint measures when the primary content of a page is visible
Minimize main-thread work
3.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoids an excessive DOM size
353 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 chaining critical requests
23 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
Avoid long main-thread tasks
11 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
Potential savings of 60 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
Max Potential First Input Delay
150 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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 1,110 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
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
Eliminate render-blocking resources
Potential savings of 3,350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoids enormous network payloads
Total size was 743 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize third-party usage
Third-party code blocked the main thread for 190 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 element
1 element found
This is the largest contentful element painted within the viewport
Document uses legible font sizes
99.93% 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 serving legacy JavaScript to modern browsers
Potential savings of 0 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
JavaScript execution time
1.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint
4.2 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
User Timing marks and measures
3 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Time to Interactive
7.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Remove unused JavaScript
Potential savings of 210 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Estimated Input Latency
20 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
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
Warning! Not found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
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 13 Links | Relationship | HTTP Status |
| Home | Internal Link | 301 |
| Publisher Rates | Internal Link | 301 |
| Advertising | Internal Link | 301 |
| Pro | Internal Link | 301 |
| Login | Internal Link | 301 |
| Register | Internal Link | 301 |
| Create Your Account | Internal Link | 301 |
| FAQ | Internal Link | 301 |
| Privacy Policy | Internal Link | 301 |
| Payments Policy | Internal Link | 301 |
| Terms Of Use | Internal Link | 301 |
| Contact Us | Internal Link | 301 |
| DMCA | Internal Link | 301 |
Alexa Rank
1,553
Local Rank: VE / Users: 79.5% / PageViews: 73.6%154,624
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| linkrex.co | Already Registered |
| linkrex.us | Already Registered |
| linkrex.com | Already Registered |
| linkrex.org | Already Registered |
| linkrex.net | Already Registered |
| lnkrex.net | Already Registered |
| oinkrex.net | Already Registered |
| pinkrex.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: Sun, 11 Oct 2020 00:20:47 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=dc4dad88c1f7d2009b15c8fc08d7c2b3c1602375647; expires=Tue, 10-Nov-20 00:20:47 GMT; path=/; domain=.linkrex.net; HttpOnly; SameSite=Lax
x-frame-options: SAMEORIGIN
set-cookie: AppSession=hge7ac6ap7r6hfsltj199mepp5; path=/; HttpOnly
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
vary: User-Agent
cf-cache-status: DYNAMIC
cf-request-id: 05b6a118a70000eb8d6632c200000001
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?lkg-colo=12&lkg-time=1602375648"}],"group":"cf-nel","max_age":604800}
nel: {"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 5e046ad43ca9eb8d-LAX
content-encoding: gzip
Click to Add/Show Comments