Fortunecapital.Asia - Info fortunecapital.asia

fortunecapital.asia receives about 339 unique visitors and 1,188 (3.50 per visitor) page views per day which should earn about $1.75/day from advertising revenue. Estimated site value is $662.52. According to Alexa Traffic Rank fortunecapital.asia is ranked number 1,471,551 in the world and 2.0E-5% of global Internet users visit it. Site is hosted in United States and links to network IP address 104.24.109.86. This server supports HTTPS and HTTP/2.

About - fortunecapital.asia


fortunecapital.asia Profile

Title: Just a moment...
Last update was 16 hours ago
loader
This can take up to 60 seconds. Please wait...

Update will be available in 8 hours
*HypeStat.com is not linking to, promoting or affiliated with fortunecapital.asia in any way. Only publicly available statistics data are displayed.

How popular is fortunecapital.asia?

339 daily visitors
Daily Unique Visitors:
339
Monthly Unique Visitors:
10,170
Pages per Visit:
3.50
Daily Pageviews:
1,188
Alexa Rank:
1,471,551 visit alexa
Alexa Reach:
2.0E-5%   (of global internet users)
Avg. visit duration:
22:32
Bounce rate:
21.03%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
59.81%
Referral:
31.35%
Search:
8.84%
Social:
0%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
Viet Nam 55.3%46.8%11910
Malaysia 25.0%28.0%20202
Indonesia 17.1%23.2%39212

Where do visitors go on this site?

Reach%Pageviews%PerUser
fortunecapital.asia
100.00%100.00%3.3

Competitive Data

SEMrush
Domain:
  fortunecapital.asia
Rank:
(Rank based on keywords, cost and organic traffic)
  405,905
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

Data

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

How socially engaged is fortunecapital.asia?

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:
fortunecapital.asia
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:
fortunecapital.asia
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 fortunecapital.asia can earn?

Daily Revenue:
$1.75
Monthly Revenue:
$52.50
Yearly Revenue:
$638.75
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Malaysia 333$1.01
Viet Nam 556$0.41
Indonesia 276$0.34

How much money do fortunecapital.asia lose due to Adblock?

Daily Revenue Loss:
$0.29
Monthly Revenue Loss:
$8.80
Yearly Revenue Loss:
$107.12
Daily Pageviews Blocked:
209
Monthly Pageviews Blocked:
6,261
Yearly Pageviews Blocked:
76,178
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Indonesia 160$0.20
Malaysia 27$0.08
Viet Nam 22$0.02

How much is fortunecapital.asia worth?

Website Value:
$662.52

Where is fortunecapital.asia hosted?

Server IP:
104.24.109.86
ASN:
AS13335 
ISP:
Cloudflare Inc 
Server Location:

United States, US
 

Other sites hosted on 104.24.109.86

How fast does fortunecapital.asia load?

Average Load Time:
(1020 ms) 79 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

85
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

Speed Index 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.4 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 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 50 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.4 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.

Screenshot Thumbnails

This is what the load of your site looked like.

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

URL
SizePotential Savings
https://fortunecapital.asia/logo.png
145 KB131 KB
https://fortunecapital.asia/img/bg-01.jpg
155 KB68 KB
https://fortunecapital.asia/img/long-gold-btn-bg.png
12 KB10 KB
Remove unused CSS - Potential savings of 61 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://fortunecapital.asia/css/user_auth.css?id=ea0c8b43f8f6aca33c22
60 KB59 KB
.swal-icon--error{border-color:#f27474;-webkit-animation:animateErrorIcon .5s; ... } ...
2 KB2 KB
Avoids enormous network payloads - Total size was 1,163 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://fortunecapital.asia/js/user_auth.js?id=76315a6dbc238c7aa575
510 KB
https://fortunecapital.asia/img/bg-01.jpg
156 KB
https://fortunecapital.asia/logo.png
145 KB
https://fortunecapital.asia/webfonts/fa-solid-900.woff2
73 KB
https://fortunecapital.asia/css/user_auth.css?id=ea0c8b43f8f6aca33c22
60 KB
https://fortunecapital.asia/font/roboto/Roboto-Bold.woff2
49 KB
https://fortunecapital.asia/font/roboto/Roboto-Light.woff2
49 KB
https://fortunecapital.asia/font/roboto/Roboto-Regular.woff2
49 KB
https://fortunecapital.asia/img/auth-foot.png
28 KB
https://fortunecapital.asia/fonts/Linearicons-Free.woff2?w118d
22 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
81 ms
Other
51 ms
Style & Layout
44 ms
Script Parsing & Compilation
22 ms
Parse HTML & CSS
20 ms
Rendering
11 ms
Serve images in next-gen formats - Potential savings of 144 KB
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.

URL
SizePotential Savings
https://fortunecapital.asia/logo.png
145 KB97 KB
https://fortunecapital.asia/img/auth-foot.png
28 KB19 KB
https://fortunecapital.asia/img/bg-01.jpg
155 KB17 KB
https://fortunecapital.asia/img/long-gold-btn-bg.png
12 KB11 KB
Avoids an excessive DOM size - 80 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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
80
Maximum DOM Depth
12
Maximum Child Elements
12
Avoid multiple page redirects - Potential savings of 340 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://fortunecapital.asia/)
0
https://fortunecapital.asia/
190
https://fortunecapital.asia/login
150
Keep request counts low and transfer sizes small - 15 requests • 1,163 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
151163 KB
Script
1510 KB
Image
5347 KB
Font
5241 KB
Stylesheet
160 KB
Document
13 KB
Other
21 KB
Media
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 150 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://fortunecapital.asia/css/user_auth.css?id=ea0c8b43f8f6aca33c22
60 KB150
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://fortunecapital.asia/
0 ms472 ms0 KB0 KB302text/html
https://fortunecapital.asia/
472 ms1382 ms1 KB0 KB302text/html
https://fortunecapital.asia/login
1382 ms2294 ms3 KB11 KB200text/htmlDocument
https://fortunecapital.asia/css/user_auth.css?id=ea0c8b43f8f6aca33c22
2304 ms2386 ms60 KB500 KB200text/cssStylesheet
https://fortunecapital.asia/logo.png
2304 ms2389 ms145 KB145 KB200image/pngImage
https://fortunecapital.asia/captcha/default?4rS8vWtp
2305 ms3330 ms5 KB4 KB200image/pngImage
https://fortunecapital.asia/img/auth-foot.png
2306 ms3337 ms28 KB28 KB200image/pngImage
https://fortunecapital.asia/js/user_auth.js?id=76315a6dbc238c7aa575
2305 ms3335 ms510 KB1531 KB200application/javascriptScript
https://fortunecapital.asia/img/bg-01.jpg
2412 ms3338 ms156 KB155 KB200image/jpegImage
https://fortunecapital.asia/img/long-gold-btn-bg.png
2414 ms3338 ms13 KB12 KB200image/pngImage
https://fortunecapital.asia/font/roboto/Roboto-Light.woff2
2414 ms3338 ms49 KB48 KB200font/woff2Font
https://fortunecapital.asia/font/roboto/Roboto-Bold.woff2
2415 ms3339 ms49 KB49 KB200font/woff2Font
https://fortunecapital.asia/font/roboto/Roboto-Regular.woff2
2415 ms3339 ms49 KB48 KB200font/woff2Font
https://fortunecapital.asia/webfonts/fa-solid-900.woff2
2415 ms3339 ms73 KB73 KB200font/woff2Font
https://fortunecapital.asia/fonts/Linearicons-Free.woff2?w118d
2415 ms3340 ms22 KB21 KB200font/woff2Font
Serve static assets with an efficient cache policy - 11 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://fortunecapital.asia/js/user_auth.js?id=76315a6dbc238c7aa575
14400000 ms510 KB
https://fortunecapital.asia/img/bg-01.jpg
14400000 ms156 KB
https://fortunecapital.asia/logo.png
14400000 ms145 KB
https://fortunecapital.asia/webfonts/fa-solid-900.woff2
14400000 ms73 KB
https://fortunecapital.asia/css/user_auth.css?id=ea0c8b43f8f6aca33c22
14400000 ms60 KB
https://fortunecapital.asia/font/roboto/Roboto-Bold.woff2
14400000 ms49 KB
https://fortunecapital.asia/font/roboto/Roboto-Light.woff2
14400000 ms49 KB
https://fortunecapital.asia/font/roboto/Roboto-Regular.woff2
14400000 ms49 KB
https://fortunecapital.asia/img/auth-foot.png
14400000 ms28 KB
https://fortunecapital.asia/fonts/Linearicons-Free.woff2?w118d
14400000 ms22 KB
https://fortunecapital.asia/img/long-gold-btn-bg.png
14400000 ms13 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
2314 ms
6 ms
2405 ms
16 ms
2422 ms
35 ms
2458 ms
6 ms
3375 ms
7 ms
3381 ms
6 ms
3388 ms
108 ms
3495 ms
6 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://fortunecapital.asia/font/roboto/Roboto-Light.woff2
924 ms
https://fortunecapital.asia/font/roboto/Roboto-Bold.woff2
924 ms
https://fortunecapital.asia/font/roboto/Roboto-Regular.woff2
924 ms
https://fortunecapital.asia/webfonts/fa-solid-900.woff2
925 ms
https://fortunecapital.asia/fonts/Linearicons-Free.woff2?w118d
925 ms
JavaScript execution time - 0.1 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
124 ms4 ms1 ms
https://fortunecapital.asia/js/user_auth.js?id=76315a6dbc238c7aa575
104 ms76 ms21 ms
Minimize Critical Requests Depth - 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. Learn more.

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

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. 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.

Reduce server response times (TTFB) - Root document took 910 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.

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

Minify CSS
Minifying CSS files can reduce network payload sizes. 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.


Page Speed (Google PageSpeed Insights) - Mobile

66
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW 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.

First Contentful Paint (FCP)3.8s 0% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 38% 38% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 38% 23% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 23%
First Input Delay (FID)61ms 94% of loads for this page have a fast (<50ms) First Input Delay (FID) 94% 3% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 3% 2% of loads for this page have a slow (>250ms) First Input Delay (FID) 2%

Origin Data

All pages served from this origin have an SLOW 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.

First Contentful Paint (FCP)3.1s 39% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 39% 44% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 44% 16% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 16%
First Input Delay (FID)219ms 0% of loads for this page have a fast (<50ms) First Input Delay (FID) 91% 3% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 3% 4% of loads for this page have a slow (>250ms) First Input Delay (FID) 4%

Lab Data

First Contentful Paint 1.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
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.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 270 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 5.3 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) 3420 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 8.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 4.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 1,163 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://fortunecapital.asia/js/user_auth.js?id=76315a6dbc238c7aa575
510 KB
https://fortunecapital.asia/img/bg-01.jpg
156 KB
https://fortunecapital.asia/logo.png
145 KB
https://fortunecapital.asia/webfonts/fa-solid-900.woff2
73 KB
https://fortunecapital.asia/css/user_auth.css?id=ea0c8b43f8f6aca33c22
60 KB
https://fortunecapital.asia/font/roboto/Roboto-Bold.woff2
49 KB
https://fortunecapital.asia/font/roboto/Roboto-Light.woff2
49 KB
https://fortunecapital.asia/font/roboto/Roboto-Regular.woff2
49 KB
https://fortunecapital.asia/img/auth-foot.png
28 KB
https://fortunecapital.asia/fonts/Linearicons-Free.woff2?w118d
22 KB
Minimizes main-thread work - 1.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
466 ms
Style & Layout
241 ms
Other
236 ms
Parse HTML & CSS
131 ms
Script Parsing & Compilation
88 ms
Rendering
64 ms
Serve images in next-gen formats - Potential savings of 144 KB
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.

URL
SizePotential Savings
https://fortunecapital.asia/logo.png
145 KB97 KB
https://fortunecapital.asia/img/auth-foot.png
28 KB19 KB
https://fortunecapital.asia/img/bg-01.jpg
155 KB17 KB
https://fortunecapital.asia/img/long-gold-btn-bg.png
12 KB11 KB
Avoids an excessive DOM size - 80 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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
80
Maximum DOM Depth
12
Maximum Child Elements
12
Avoid multiple page redirects - Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://fortunecapital.asia/)
0
https://fortunecapital.asia/
630
https://fortunecapital.asia/login
480
Keep request counts low and transfer sizes small - 15 requests • 1,163 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
151163 KB
Script
1510 KB
Image
5346 KB
Font
5241 KB
Stylesheet
160 KB
Document
13 KB
Other
21 KB
Media
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 480 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://fortunecapital.asia/css/user_auth.css?id=ea0c8b43f8f6aca33c22
60 KB480
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://fortunecapital.asia/
0 ms588 ms0 KB0 KB302text/html
https://fortunecapital.asia/
589 ms1595 ms1 KB0 KB302text/html
https://fortunecapital.asia/login
1596 ms2608 ms3 KB11 KB200text/htmlDocument
https://fortunecapital.asia/css/user_auth.css?id=ea0c8b43f8f6aca33c22
2621 ms2702 ms60 KB500 KB200text/cssStylesheet
https://fortunecapital.asia/logo.png
2621 ms2707 ms145 KB145 KB200image/pngImage
https://fortunecapital.asia/captcha/default?fyua674t
2621 ms3691 ms4 KB4 KB200image/pngImage
https://fortunecapital.asia/img/auth-foot.png
2627 ms3698 ms28 KB28 KB200image/pngImage
https://fortunecapital.asia/js/user_auth.js?id=76315a6dbc238c7aa575
2626 ms3696 ms510 KB1531 KB200application/javascriptScript
https://fortunecapital.asia/img/bg-01.jpg
2731 ms3746 ms156 KB155 KB200image/jpegImage
https://fortunecapital.asia/img/long-gold-btn-bg.png
2733 ms3769 ms13 KB12 KB200image/pngImage
https://fortunecapital.asia/font/roboto/Roboto-Light.woff2
2736 ms3812 ms49 KB48 KB200font/woff2Font
https://fortunecapital.asia/font/roboto/Roboto-Bold.woff2
2737 ms3813 ms49 KB49 KB200font/woff2Font
https://fortunecapital.asia/font/roboto/Roboto-Regular.woff2
2737 ms3813 ms49 KB48 KB200font/woff2Font
https://fortunecapital.asia/webfonts/fa-solid-900.woff2
2737 ms3814 ms73 KB73 KB200font/woff2Font
https://fortunecapital.asia/fonts/Linearicons-Free.woff2?w118d
2737 ms3984 ms22 KB21 KB200font/woff2Font
Serve static assets with an efficient cache policy - 11 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://fortunecapital.asia/js/user_auth.js?id=76315a6dbc238c7aa575
14400000 ms510 KB
https://fortunecapital.asia/img/bg-01.jpg
14400000 ms156 KB
https://fortunecapital.asia/logo.png
14400000 ms145 KB
https://fortunecapital.asia/webfonts/fa-solid-900.woff2
14400000 ms73 KB
https://fortunecapital.asia/css/user_auth.css?id=ea0c8b43f8f6aca33c22
14400000 ms60 KB
https://fortunecapital.asia/font/roboto/Roboto-Bold.woff2
14400000 ms49 KB
https://fortunecapital.asia/font/roboto/Roboto-Light.woff2
14400000 ms49 KB
https://fortunecapital.asia/font/roboto/Roboto-Regular.woff2
14400000 ms49 KB
https://fortunecapital.asia/img/auth-foot.png
14400000 ms28 KB
https://fortunecapital.asia/fonts/Linearicons-Free.woff2?w118d
14400000 ms22 KB
https://fortunecapital.asia/img/long-gold-btn-bg.png
14400000 ms13 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
2629 ms
8 ms
2638 ms
10 ms
2722 ms
17 ms
2741 ms
48 ms
2790 ms
7 ms
3748 ms
137 ms
3886 ms
11 ms
3898 ms
5 ms
3919 ms
6 ms
3925 ms
9 ms
4003 ms
10 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://fortunecapital.asia/font/roboto/Roboto-Light.woff2
1076 ms
https://fortunecapital.asia/font/roboto/Roboto-Bold.woff2
1076 ms
https://fortunecapital.asia/font/roboto/Roboto-Regular.woff2
1077 ms
https://fortunecapital.asia/webfonts/fa-solid-900.woff2
1077 ms
https://fortunecapital.asia/fonts/Linearicons-Free.woff2?w118d
1247 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
657 ms21 ms4 ms
https://fortunecapital.asia/js/user_auth.js?id=76315a6dbc238c7aa575
564 ms442 ms83 ms
Properly size images - Potential savings of 82 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
https://fortunecapital.asia/img/bg-01.jpg
155 KB43 KB
https://fortunecapital.asia/logo.png
145 KB39 KB
Remove unused CSS - Potential savings of 61 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://fortunecapital.asia/css/user_auth.css?id=ea0c8b43f8f6aca33c22
60 KB59 KB
.swal-icon--error{border-color:#f27474;-webkit-animation:animateErrorIcon .5s; ... } ...
2 KB2 KB
Minimize Critical Requests Depth - 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. Learn more.

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

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. 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.

Reduce server response times (TTFB) - Root document took 1,010 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.

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

Minify CSS
Minifying CSS files can reduce network payload sizes. 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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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:

http://fortunecapital.asia/img-sys/IP_changed.png (4 hours)
http://fortunecapital.asia/img-sys/powered_by_cpanel.svg (4 hours)
http://fortunecapital.asia/img-sys/server_misconfigured.png (4 hours)
http://fortunecapital.asia/img-sys/server_moved.png (4 hours)
http://fortunecapital.asia/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js (2 days)

Reduce server response time

In our test, your server responded in 0.22 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.

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 1.1KiB (13% reduction).

Compressing http://fortunecapital.asia/img-sys/server_moved.png could save 407B (13% reduction).
Compressing http://fortunecapital.asia/img-sys/server_misconfigured.png could save 388B (13% reduction).
Compressing http://fortunecapital.asia/img-sys/IP_changed.png could save 357B (13% reduction).

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 209B (11% reduction).

Minifying http://fortunecapital.asia/cgi-sys/defaultwebpage.cgi could save 209B (11% reduction) after compression.
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.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
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.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
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.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Enable compression
You have compression enabled. Learn more about enabling compression.
Download optimized image, JavaScript, and CSS resources for this page.

Does fortunecapital.asia use compression?

fortunecapital.asia use gzip compression.
Original size: 8.9 KB
Compressed size: 149 B
File reduced by: 8.75 KB (98%)

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

fortunecapital.asia supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: sni.cloudflaressl.com
Organization:
Location:
Issuer: CloudFlare Inc ECC CA-2
Valid from: May 13 00:00:00 2019 GMT
Valid until: May 13 12:00:00 2020 GMT
Authority:
Keysize:

Verify HTTP/2 Support

fortunecapital.asia supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

Http Header

Date: Sun, 16 Jun 2019 08:08:18 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Set-Cookie: __cfduid=dddaabdbc5447ec402b30a9339313b6171560672498; expires=Mon, 15-Jun-20 08:08:18 GMT; path=/; domain=.fortunecapital.asia; HttpOnly
X-Frame-Options: SAMEORIGIN
Cache-Control: no-cache
Vary: Accept-Encoding
Server: cloudflare
CF-RAY: 4e7b4b88fb2e41e1-MSP

DNS Lookup

Type Ip Target TTL
HINFO 3600
A 104.24.108.86 265
A 104.24.109.86 265
NS sue.ns.cloudflare.com 3565
NS skip.ns.cloudflare.com 3565

Whois Lookup

Domain Created:
2019-04-29
Domain Age:
1 months 17 days  
WhoIs:
 

whois lookup at whois.nic.asia...
Domain Name: FORTUNECAPITAL.ASIA
Registry Domain ID: D425500000112148827-AGRS
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2019-05-13T14:16:51Z
Creation Date: 2019-04-29T06:12:11Z
Registry Expiry Date: 2020-04-29T06:12:11Z
Registrar Registration Expiration Date:
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.4806242505
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
Registrant Organization: Domains By Proxy, LLC
Registrant State/Province: Arizona
Registrant Country: US
Name Server: SUE.NS.CLOUDFLARE.COM
Name Server: SKIP.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2019-06-16T08:07:53Z <<<

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

Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by The Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no cir***stances will you use this data 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 data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Registry Operator reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Last update was 16 hours ago
loader
This can take up to 60 seconds. Please wait...

Update will be available in 8 hours
*HypeStat.com is not linking to, promoting or affiliated with fortunecapital.asia in any way. Only publicly available statistics data are displayed.

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!
fortunecapital.asia widget