Xman.Life - Info xman.life

xman.life receives about 272 unique visitors and 272 (1.00 per visitor) page views per day which should earn about $1.11/day from advertising revenue. Estimated site value is $810.65. According to Alexa Traffic Rank xman.life is ranked number 4,755,793 in the world and 6.0E-6% of global Internet users visit it. Site is hosted in Provo, Utah, 84606, United States and links to network IP address 162.241.203.196. This server supports HTTPS and HTTP/2.

About - xman.life


Technologies used on Website

Web Servers
Apache
Analytics
Google Analytics
CMS
WordPress
Blogs
WordPress
JavaScript Libraries
jQuery Migrate
jQuery
Programming Languages
PHP
Databases
MySQL

xman.life Profile

Title: xman.life – Just another WordPress site
Last update was 129 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with xman.life in any way. Only publicly available statistics data are displayed.

How popular is xman.life?

272 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
272
Monthly Unique Visitors:
6,528
Pages per Visit:
1.00
Daily Pageviews:
272
Alexa Rank:
4,755,793 visit alexa
Alexa Reach:
6.0E-6%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  xman.life
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is xman.life?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
xman.life
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
xman.life
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much xman.life can earn?

Daily Revenue:
$1.11
Monthly Revenue:
$33.30
Yearly Revenue:
$405.15
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do xman.life lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is xman.life worth?

Website Value:
$810.65

+ Where is xman.life hosted?

Server IP:
162.241.203.196
ASN:
AS46606 
ISP:
Unified Layer 
Server Location:
Provo
Utah, UT
84606
United States, US
 

Other sites hosted on 162.241.203.196

+ How fast does xman.life load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

87
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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. Learn more.
Speed Index 1.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
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.
First Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 97 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). Learn more.

Statistic
ElementValue
Total DOM Elements
97
Maximum DOM Depth
11
Maximum Child Elements
6
Minify JavaScript - Potential savings of 6 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.fancybox.js?ver=100.1.5
18 KB6 KB
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://xman.life/)
0
https://xman.life/
190
Keep request counts low and transfer sizes small - 23 requests • 229 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
23229 KB
Script
12139 KB
Stylesheet
664 KB
Other
219 KB
Document
15 KB
Font
11 KB
Image
11 KB
Media
00 KB
Third-party
438 KB
Eliminate render-blocking resources - Potential savings of 870 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://xman.life/wp-includes/css/dist/block-library/style.min.css?ver=5.3
8 KB110
https://xman.life/wp-includes/css/dist/block-library/theme.min.css?ver=5.3
1 KB150
https://xman.life/wp-content/plugins/ecwid-shopping-cart/css/frontend.css?ver=6.8.8
1 KB150
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
51 KB390
https://xman.life/wp-content/plugins/wp-max-seo/css/jquery.fancybox.css?ver=5.3
2 KB150
https://xman.life/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
42 KB350
https://xman.life/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
5 KB70
https://xman.life/wp-content/plugins/ecwid-shopping-cart/js/frontend.js?ver=6.8.8
2 KB70
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery-1.11.1.js?ver=100.1.5
42 KB270
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.mousewheel-3.0.6.pack.js?ver=100.1.5
1 KB70
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.fancybox.js?ver=100.1.5
18 KB150
https://xman.life/wp-content/plugins/wp-max-seo/js/seo.js?ver=100.1.5
3 KB70
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://xman.life/
0 ms422 ms0 KB0 KB301text/html
https://xman.life/
422 ms800 ms5 KB14 KB200text/htmlDocument
https://xman.life/wp-includes/css/dist/block-library/style.min.css?ver=5.3
811 ms978 ms8 KB40 KB200text/cssStylesheet
https://xman.life/wp-includes/css/dist/block-library/theme.min.css?ver=5.3
812 ms974 ms1 KB2 KB200text/cssStylesheet
https://xman.life/wp-content/plugins/ecwid-shopping-cart/css/frontend.css?ver=6.8.8
812 ms977 ms1 KB2 KB200text/cssStylesheet
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
812 ms1677 ms51 KB208 KB200text/cssStylesheet
https://xman.life/wp-content/plugins/wp-max-seo/css/jquery.fancybox.css?ver=5.3
813 ms990 ms2 KB5 KB200text/cssStylesheet
https://xman.life/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
813 ms1058 ms42 KB95 KB200application/javascriptScript
https://xman.life/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
813 ms1077 ms5 KB10 KB200application/javascriptScript
https://xman.life/wp-content/plugins/ecwid-shopping-cart/js/frontend.js?ver=6.8.8
814 ms975 ms2 KB4 KB200application/javascriptScript
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery-1.11.1.js?ver=100.1.5
814 ms943 ms42 KB94 KB200application/javascriptScript
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.mousewheel-3.0.6.pack.js?ver=100.1.5
814 ms976 ms1 KB1 KB200application/javascriptScript
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.fancybox.js?ver=100.1.5
814 ms1035 ms18 KB50 KB200application/javascriptScript
https://xman.life/wp-content/plugins/wp-max-seo/js/seo.js?ver=100.1.5
814 ms975 ms3 KB7 KB200application/javascriptScript
https://xman.life/wp-includes/js/jquery/ui/widget.min.js?ver=1.11.4
815 ms974 ms3 KB7 KB200application/javascriptScript
https://xman.life/wp-content/plugins/wp-max-seo/js/auto-link.js?ver=100.1.5
815 ms982 ms1 KB1 KB200application/javascriptScript
https://xman.life/wp-includes/js/wp-embed.min.js?ver=5.3
815 ms1975 ms1 KB1 KB200application/javascriptScript
https://app.ecwid.com/script.js?13433173&data_platform=wporg&lang=pt&data_g=0000000000
816 ms905 ms19 KB0 KB200text/javascriptOther
https://xman.life/wp-includes/js/wp-emoji-release.min.js?ver=5.3
844 ms1003 ms5 KB14 KB200application/javascriptScript
https://xman.life/wp-content/themes/twentynineteen/print.css?ver=1.4
906 ms1064 ms2 KB4 KB200text/cssStylesheet
https://www.google-analytics.com/analytics.js
1756 ms1761 ms18 KB43 KB200text/javascriptScript
data:application/font-woff2;charset=utf-8;base64,d09GMgABAAAAAAMoAA0AAAAACDQAAALTAAEAAAAAAAAAAAAAAAA
1770 ms1817 ms1 KB1 KB200application/font-woff2Font
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=191973755&t=pageview&_s=1&dl=https%3A%2F%2Fxman.life%2F&ul=en-us&de=UTF-8&dt=xman.life%20%E2%80%93%20Just%20another%20WordPress%20site&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEAB~&jid=441733939&gjid=225342776&cid=1048758829.1574535565&tid=UA-146799802-2&_gid=137795171.1574535565&_r=1&z=1317465033
1862 ms1868 ms1 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
0 ms51 KB
https://xman.life/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
0 ms42 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery-1.11.1.js?ver=100.1.5
0 ms42 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.fancybox.js?ver=100.1.5
0 ms18 KB
https://xman.life/wp-includes/css/dist/block-library/style.min.css?ver=5.3
0 ms8 KB
https://xman.life/wp-includes/js/wp-emoji-release.min.js?ver=5.3
0 ms5 KB
https://xman.life/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
0 ms5 KB
https://xman.life/wp-includes/js/jquery/ui/widget.min.js?ver=1.11.4
0 ms3 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/seo.js?ver=100.1.5
0 ms3 KB
https://xman.life/wp-content/plugins/wp-max-seo/css/jquery.fancybox.css?ver=5.3
0 ms2 KB
https://xman.life/wp-content/plugins/ecwid-shopping-cart/js/frontend.js?ver=6.8.8
0 ms2 KB
https://xman.life/wp-content/themes/twentynineteen/print.css?ver=1.4
0 ms2 KB
https://xman.life/wp-includes/js/wp-embed.min.js?ver=5.3
0 ms1 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.mousewheel-3.0.6.pack.js?ver=100.1.5
0 ms1 KB
https://xman.life/wp-includes/css/dist/block-library/theme.min.css?ver=5.3
0 ms1 KB
https://xman.life/wp-content/plugins/ecwid-shopping-cart/css/frontend.css?ver=6.8.8
0 ms1 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/auto-link.js?ver=100.1.5
0 ms1 KB
https://www.google-analytics.com/analytics.js
7200000 ms18 KB
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. Learn more.

Third-Party
SizeMain-Thread Blocking Time
19 KB0 ms
19 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
823 ms
6 ms
832 ms
35 ms
1700 ms
10 ms
1717 ms
21 ms
1749 ms
19 ms
1780 ms
57 ms
1841 ms
11 ms
1854 ms
30 ms
1997 ms
28 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
134 ms4 ms1 ms
Minify CSS - Potential savings of 8 KB
Minifying CSS files can reduce network payload sizes. Learn more.

URL
SizePotential Savings
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
51 KB8 KB
Remove unused CSS - Potential savings of 48 KB
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. Learn more.

URL
SizePotential Savings
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
51 KB48 KB
Avoids enormous network payloads - Total size was 229 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
51 KB
https://xman.life/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
42 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery-1.11.1.js?ver=100.1.5
42 KB
https://app.ecwid.com/script.js?13433173&data_platform=wporg&lang=pt&data_g=0000000000
19 KB
https://www.google-analytics.com/analytics.js
18 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.fancybox.js?ver=100.1.5
18 KB
https://xman.life/wp-includes/css/dist/block-library/style.min.css?ver=5.3
8 KB
https://xman.life/
5 KB
https://xman.life/wp-includes/js/wp-emoji-release.min.js?ver=5.3
5 KB
https://xman.life/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
5 KB
Minimizes main-thread work - 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
122 ms
Style & Layout
67 ms
Other
37 ms
Parse HTML & CSS
24 ms
Script Parsing & Compilation
14 ms
Rendering
7 ms
Serve images in next-gen formats
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. Learn more.

Avoid chaining critical requests - 16 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 380 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

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. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

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. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

64
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 3.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 3.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
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. Learn more.
First Contentful Paint (3G) 7335 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 7.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 3.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 3.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 97 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). Learn more.

Statistic
ElementValue
Total DOM Elements
97
Maximum DOM Depth
11
Maximum Child Elements
6
Minify JavaScript - Potential savings of 6 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.fancybox.js?ver=100.1.5
18 KB6 KB
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://xman.life/)
0
https://xman.life/
630
Keep request counts low and transfer sizes small - 23 requests • 229 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
23229 KB
Script
12139 KB
Stylesheet
664 KB
Other
219 KB
Document
15 KB
Font
11 KB
Image
11 KB
Media
00 KB
Third-party
438 KB
Eliminate render-blocking resources - Potential savings of 2,490 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://xman.life/wp-includes/css/dist/block-library/style.min.css?ver=5.3
8 KB480
https://xman.life/wp-includes/css/dist/block-library/theme.min.css?ver=5.3
1 KB480
https://xman.life/wp-content/plugins/ecwid-shopping-cart/css/frontend.css?ver=6.8.8
1 KB480
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
51 KB1680
https://xman.life/wp-content/plugins/wp-max-seo/css/jquery.fancybox.css?ver=5.3
2 KB480
https://xman.life/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
42 KB1530
https://xman.life/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
5 KB330
https://xman.life/wp-content/plugins/ecwid-shopping-cart/js/frontend.js?ver=6.8.8
2 KB180
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery-1.11.1.js?ver=100.1.5
42 KB1230
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.mousewheel-3.0.6.pack.js?ver=100.1.5
1 KB180
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.fancybox.js?ver=100.1.5
18 KB630
https://xman.life/wp-content/plugins/wp-max-seo/js/seo.js?ver=100.1.5
3 KB180
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://xman.life/
0 ms410 ms0 KB0 KB301text/html
https://xman.life/
410 ms921 ms5 KB14 KB200text/htmlDocument
https://xman.life/wp-includes/css/dist/block-library/style.min.css?ver=5.3
936 ms1168 ms8 KB40 KB200text/cssStylesheet
https://xman.life/wp-includes/css/dist/block-library/theme.min.css?ver=5.3
936 ms1101 ms1 KB2 KB200text/cssStylesheet
https://xman.life/wp-content/plugins/ecwid-shopping-cart/css/frontend.css?ver=6.8.8
936 ms984 ms1 KB2 KB200text/cssStylesheet
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
937 ms1185 ms51 KB208 KB200text/cssStylesheet
https://xman.life/wp-content/plugins/wp-max-seo/css/jquery.fancybox.css?ver=5.3
937 ms1100 ms2 KB5 KB200text/cssStylesheet
https://xman.life/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
937 ms3492 ms42 KB95 KB200application/javascriptScript
https://xman.life/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
937 ms1151 ms5 KB10 KB200application/javascriptScript
https://xman.life/wp-content/plugins/ecwid-shopping-cart/js/frontend.js?ver=6.8.8
938 ms1101 ms2 KB4 KB200application/javascriptScript
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery-1.11.1.js?ver=100.1.5
938 ms1241 ms42 KB94 KB200application/javascriptScript
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.mousewheel-3.0.6.pack.js?ver=100.1.5
938 ms1103 ms1 KB1 KB200application/javascriptScript
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.fancybox.js?ver=100.1.5
938 ms1190 ms18 KB50 KB200application/javascriptScript
https://xman.life/wp-content/plugins/wp-max-seo/js/seo.js?ver=100.1.5
939 ms1109 ms3 KB7 KB200application/javascriptScript
https://xman.life/wp-includes/js/jquery/ui/widget.min.js?ver=1.11.4
939 ms1113 ms3 KB7 KB200application/javascriptScript
https://xman.life/wp-content/plugins/wp-max-seo/js/auto-link.js?ver=100.1.5
939 ms1101 ms1 KB1 KB200application/javascriptScript
https://xman.life/wp-includes/js/wp-embed.min.js?ver=5.3
939 ms1100 ms1 KB1 KB200application/javascriptScript
https://app.ecwid.com/script.js?13433173&data_platform=wporg&lang=pt&data_g=0000000000
940 ms969 ms19 KB0 KB200text/javascriptOther
https://xman.life/wp-includes/js/wp-emoji-release.min.js?ver=5.3
980 ms1032 ms5 KB14 KB200application/javascriptScript
https://xman.life/wp-content/themes/twentynineteen/print.css?ver=1.4
983 ms1158 ms2 KB4 KB200text/cssStylesheet
https://www.google-analytics.com/analytics.js
3548 ms3554 ms18 KB43 KB200text/javascriptScript
data:application/font-woff2;charset=utf-8;base64,d09GMgABAAAAAAMoAA0AAAAACDQAAALTAAEAAAAAAAAAAAAAAAA
3558 ms3607 ms1 KB1 KB200application/font-woff2Font
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=1675809951&t=pageview&_s=1&dl=https%3A%2F%2Fxman.life%2F&ul=en-us&de=UTF-8&dt=xman.life%20%E2%80%93%20Just%20another%20WordPress%20site&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=IEBAAEAB~&jid=1380206294&gjid=1945614980&cid=2085430964.1574535558&tid=UA-146799802-2&_gid=1348125297.1574535558&_r=1&z=743550882
3645 ms3650 ms1 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
0 ms51 KB
https://xman.life/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
0 ms42 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery-1.11.1.js?ver=100.1.5
0 ms42 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.fancybox.js?ver=100.1.5
0 ms18 KB
https://xman.life/wp-includes/css/dist/block-library/style.min.css?ver=5.3
0 ms8 KB
https://xman.life/wp-includes/js/wp-emoji-release.min.js?ver=5.3
0 ms5 KB
https://xman.life/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
0 ms5 KB
https://xman.life/wp-includes/js/jquery/ui/widget.min.js?ver=1.11.4
0 ms3 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/seo.js?ver=100.1.5
0 ms3 KB
https://xman.life/wp-content/plugins/wp-max-seo/css/jquery.fancybox.css?ver=5.3
0 ms2 KB
https://xman.life/wp-content/plugins/ecwid-shopping-cart/js/frontend.js?ver=6.8.8
0 ms2 KB
https://xman.life/wp-content/themes/twentynineteen/print.css?ver=1.4
0 ms2 KB
https://xman.life/wp-includes/js/wp-embed.min.js?ver=5.3
0 ms1 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.mousewheel-3.0.6.pack.js?ver=100.1.5
0 ms1 KB
https://xman.life/wp-includes/css/dist/block-library/theme.min.css?ver=5.3
0 ms1 KB
https://xman.life/wp-content/plugins/ecwid-shopping-cart/css/frontend.css?ver=6.8.8
0 ms1 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/auto-link.js?ver=100.1.5
0 ms1 KB
https://www.google-analytics.com/analytics.js
7200000 ms18 KB
Minimize third-party usage - Third-party code blocked the main thread for 40 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. Learn more.

Third-Party
SizeMain-Thread Blocking Time
19 KB39 ms
19 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
947 ms
9 ms
958 ms
47 ms
1210 ms
11 ms
3521 ms
18 ms
3549 ms
15 ms
3573 ms
56 ms
3633 ms
9 ms
3643 ms
25 ms
3668 ms
22 ms
JavaScript execution time - 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
519 ms17 ms4 ms
https://xman.life/
185 ms179 ms6 ms
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery-1.11.1.js?ver=100.1.5
102 ms86 ms8 ms
https://www.google-analytics.com/analytics.js
98 ms92 ms6 ms
https://xman.life/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
86 ms74 ms7 ms
Minify CSS - Potential savings of 8 KB
Minifying CSS files can reduce network payload sizes. Learn more.

URL
SizePotential Savings
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
51 KB8 KB
Remove unused CSS - Potential savings of 49 KB
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. Learn more.

URL
SizePotential Savings
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
51 KB49 KB
Avoids enormous network payloads - Total size was 229 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
51 KB
https://xman.life/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
42 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery-1.11.1.js?ver=100.1.5
42 KB
https://app.ecwid.com/script.js?13433173&data_platform=wporg&lang=pt&data_g=0000000000
19 KB
https://www.google-analytics.com/analytics.js
18 KB
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.fancybox.js?ver=100.1.5
18 KB
https://xman.life/wp-includes/css/dist/block-library/style.min.css?ver=5.3
8 KB
https://xman.life/
5 KB
https://xman.life/wp-includes/js/wp-emoji-release.min.js?ver=5.3
5 KB
https://xman.life/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
5 KB
Minimizes main-thread work - 1.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
474 ms
Style & Layout
250 ms
Other
151 ms
Parse HTML & CSS
90 ms
Script Parsing & Compilation
51 ms
Rendering
18 ms
Garbage Collection
2 ms
Serve images in next-gen formats
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. Learn more.

Avoid chaining critical requests - 16 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 510 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

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. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

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. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 7 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:

https://xman.life/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
https://xman.life/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
https://xman.life/wp-content/plugins/ecwid-shopping-cart/js/frontend.js?ver=6.8.8
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery-1.11.1.js?ver=100.1.5
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.mousewheel-3.0.6.pack.js?ver=100.1.5
https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.fancybox.js?ver=100.1.5
https://xman.life/wp-content/plugins/wp-max-seo/js/seo.js?ver=100.1.5
Optimize CSS Delivery of the following:

https://xman.life/wp-includes/css/dist/block-library/style.min.css?ver=5.3
https://xman.life/wp-includes/css/dist/block-library/theme.min.css?ver=5.3
https://xman.life/wp-content/plugins/ecwid-shopping-cart/css/frontend.css?ver=6.8.8
https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4
https://xman.life/wp-content/plugins/wp-max-seo/css/jquery.fancybox.css?ver=5.3

Reduce server response time

In our test, your server responded in 0.32 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.google-***ytics.com/***ytics.js (2 hours)

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 5.5KiB (18% reduction).

Minifying https://xman.life/wp-content/themes/twentynineteen/style.css?ver=1.4 could save 5KiB (17% reduction) after compression.
Minifying https://xman.life/wp-content/themes/twentynineteen/print.css?ver=1.4 could save 321B (27% reduction) after compression.
Minifying https://xman.life/wp-content/plugins/wp-max-seo/css/jquery.fancybox.css?ver=5.3 could save 247B (18% reduction) after compression.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 5.3KiB (31% reduction).

Minifying https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.fancybox.js?ver=100.1.5 could save 4.2KiB (31% reduction) after compression.
Minifying https://xman.life/wp-content/plugins/wp-max-seo/js/seo.js?ver=100.1.5 could save 590B (34% reduction) after compression.
Minifying https://xman.life/wp-content/plugins/wp-max-seo/js/jquery.mousewheel-3.0.6.pack.js?ver=100.1.5 could save 225B (32% reduction) after compression.
Minifying https://xman.life/wp-content/plugins/ecwid-shopping-cart/js/frontend.js?ver=6.8.8 could save 184B (16% reduction) after compression.
Minifying https://xman.life/wp-content/plugins/wp-max-seo/js/auto-link.js?ver=100.1.5 could save 113B (30% reduction) after compression.

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="https://xman.l…orld/#comments">1 comentário em Hello world!</a> is close to 2 other tap targets .
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Optimize images
Your images are optimized. Learn more about optimizing images.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does xman.life use compression?

xman.life use gzip compression.
Original size: 13.71 KB
Compressed size: 5.16 KB
File reduced by: 8.55 KB (62%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

xman.life supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: xman.life
Organization:
Location:
Issuer: Sectigo RSA Domain Validation Secure Server CA
Valid from: Aug 30 00:00:00 2019 GMT
Valid until: Nov 28 23:59:59 2019 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

xman.life supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Upgrade: h2c
Connection: Upgrade

HTTP/2 301 
date: Thu, 01 Jan 1970 00:00:00 GMT
server: Apache
x-redirect-by: WordPress
location: https://xman.life/
content-length: 0
content-type: text/html; charset=UTF-8

HTTP/2 200 
date: Sat, 23 Nov 2019 18:59:04 GMT
server: Apache
link: <https://xman.life/wp-json/>; rel="https://api.w.org/"
vary: Accept-Encoding
content-encoding: gzip
accept-ranges: none
content-length: 5284
content-type: text/html; charset=UTF-8

+ DNS Lookup

Type Ip Target TTL
SOA 3600
Mname wns148.hostgator.com.br
Rname root.wp148.hostgator.com.br
Serial Number 2019083001
Refresh 86400
Retry 7200
Expire 3600000
Minimum TTL 0
MX mail.xman.life 3600
TXT 3600
A 162.241.203.196 3573
NS wns149.hostgator.com.br 3572
NS wns148.hostgator.com.br 3572

+ Whois Lookup

Domain Created:
2019-08-29
Domain Age:
2 months 25 days  
WhoIs:
 

whois lookup at whois.donuts.co...
Domain Name: xman.life
Registry Domain ID: 1090b2b664bc43a8a0***90ea73965f10-DONUTS
Registrar WHOIS Server: whois.PublicDomainRegistry.com
Registrar URL: http://www.PublicDomainRegistry.com
Updated Date: 2019-09-03T16:25:01Z
Creation Date: 2019-08-29T16:24:37Z
Registry Expiry Date: 2020-08-29T16:24:37Z
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID: 303
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +91.2230797500
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: N/A
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: MG
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: BR
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: wns148.hostgator.com.br
Name Server: wns149.hostgator.com.br
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-11-23T18:59:29Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Terms of Use: Donuts Inc. provides this Whois service for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Donuts does not guarantee its accuracy. Users accessing the Donuts Whois service agree to use the data only for lawful purposes, and under no cir***stances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar’s own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Donuts or any ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. When using the Donuts Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data can be requested by submitting a request via the form found at https://donuts.domains/about/policies/whois-layered-access/ Donuts Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
Last update was 129 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with xman.life in any way. Only publicly available statistics data are displayed.
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
xman.life widget