Felcra.Com.My felcra.com.my

Esistem.Felcra.Com.My

esistem.felcra.com.my receives about 1,588 unique visitors and 8,097 (5.10 per visitor) page views per day which should earn about $24.53/day from advertising revenue. Estimated site value is $17,910.21. According to Alexa Traffic Rank esistem.felcra.com.my is ranked number 928,741 in the world and 3.5E-5% of global Internet users visit it. Site is hosted in Malaysia and links to network IP address 103.6.238.212. This server doesn't support HTTPS and doesn't support HTTP/2.

About - esistem.felcra.com.my


Technologies used on Website

Web Servers
IIS
Web Frameworks
Microsoft ASP.NET
Operating Systems
Windows Server

esistem.felcra.com.my Profile

Last update was 19 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is esistem.felcra.com.my?

1.6K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
1,588
Monthly Unique Visitors:
38,112
Pages per Visit:
5.10
Daily Pageviews:
8,097
Alexa Rank:
928,741 visit alexa
Alexa Reach:
3.5E-5%   (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

Users%Pageviews%Rank
Malaysia 100.0%100.0%5781

Where do visitors go on this site?

Reach%Pageviews%PerUser
pppls.felcra.com.my
78.14%92.63%7.0
OTHER
0%7.37%0

Competitive Data

SEMrush
Domain:
  esistem.felcra.com.my
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 esistem.felcra.com.my?

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:
felcra.com.my
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:
felcra.com.my
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 esistem.felcra.com.my can earn?

Daily Revenue:
$24.53
Monthly Revenue:
$735.90
Yearly Revenue:
$8,953.45
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Malaysia 8,097$24.53

How much money do esistem.felcra.com.my lose due to Adblock?

Daily Revenue Loss:
$1.96
Monthly Revenue Loss:
$58.88
Yearly Revenue Loss:
$716.39
Daily Pageviews Blocked:
648
Monthly Pageviews Blocked:
19,433
Yearly Pageviews Blocked:
236,432
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Malaysia 648$1.96

How much is esistem.felcra.com.my worth?

Website Value:
$17,910.21

+ Where is esistem.felcra.com.my hosted?

Server IP:
103.6.238.212
ASN:
AS132197 
ISP:
SKALI 
Server Location:

Malaysia, MY
 

Other sites hosted on 103.6.238.212

There are no other sites hosted on this IP

+ How fast does esistem.felcra.com.my load?

Average Load Time:
(1293 ms) 56 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

99
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 0.4 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 0.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
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.
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 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.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.4 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 - 41 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
41
Maximum DOM Depth
11
Maximum Child Elements
6
Minify JavaScript - Potential savings of 13 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js
32 KB13 KB
Keep request counts low and transfer sizes small - 5 requests • 90 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
590 KB
Image
253 KB
Script
234 KB
Document
13 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 70 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
http://esistem.felcra.com.my/flashinglinks.js
2 KB70
Enable text compression - Potential savings of 22 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js
31 KB21 KB
http://esistem.felcra.com.my/
3 KB2 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://esistem.felcra.com.my/
0 ms232 ms3 KB3 KB200text/htmlDocument
http://esistem.felcra.com.my/flashinglinks.js
241 ms472 ms2 KB2 KB200application/x-javascriptScript
http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js
241 ms717 ms32 KB31 KB200application/x-javascriptScript
http://esistem.felcra.com.my/index.gif
241 ms1391 ms37 KB37 KB200image/gifImage
http://esistem.felcra.com.my/pict/today.gif
242 ms529 ms16 KB16 KB200image/gifImage
Serve static assets with an efficient cache policy - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://esistem.felcra.com.my/index.gif
0 ms37 KB
http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js
0 ms32 KB
http://esistem.felcra.com.my/pict/today.gif
0 ms16 KB
http://esistem.felcra.com.my/flashinglinks.js
0 ms2 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
255 ms
5 ms
739 ms
9 ms
749 ms
5 ms
Properly size images - Potential savings of 16 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://esistem.felcra.com.my/pict/today.gif
16 KB16 KB
Avoids enormous network payloads - Total size was 90 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://esistem.felcra.com.my/index.gif
37 KB
http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js
32 KB
http://esistem.felcra.com.my/pict/today.gif
16 KB
http://esistem.felcra.com.my/
3 KB
http://esistem.felcra.com.my/flashinglinks.js
2 KB
Minimizes main-thread work - 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.

Category
Time Spent
Script Evaluation
25 ms
Other
17 ms
Style & Layout
5 ms
Parse HTML & CSS
2 ms
Rendering
2 ms
Script Parsing & Compilation
2 ms
Avoid chaining critical requests - 2 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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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 230 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.

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.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. 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.

Remove unused CSS
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.

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.


Page Speed (Google PageSpeed Insights) - Mobile

99
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

First Contentful Paint (3G) 2214 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. 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.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.2 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.2 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.2 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.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
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.

Screenshot Thumbnails

This is what the load of your site looked like.

Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
744 ms
8 ms
1534 ms
12 ms
1546 ms
10 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
163 ms12 ms4 ms
http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js
79 ms73 ms4 ms
Properly size images - Potential savings of 16 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://esistem.felcra.com.my/pict/today.gif
16 KB16 KB
Avoids enormous network payloads - Total size was 90 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://esistem.felcra.com.my/index.gif
37 KB
http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js
32 KB
http://esistem.felcra.com.my/pict/today.gif
16 KB
http://esistem.felcra.com.my/
3 KB
http://esistem.felcra.com.my/flashinglinks.js
2 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. Learn more.

Category
Time Spent
Script Evaluation
87 ms
Other
84 ms
Style & Layout
39 ms
Rendering
13 ms
Parse HTML & CSS
12 ms
Script Parsing & Compilation
10 ms
Avoids an excessive DOM size - 41 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
41
Maximum DOM Depth
11
Maximum Child Elements
6
Minify JavaScript - Potential savings of 13 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js
32 KB13 KB
Keep request counts low and transfer sizes small - 5 requests • 90 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
590 KB
Image
253 KB
Script
234 KB
Document
13 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 180 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
http://esistem.felcra.com.my/flashinglinks.js
2 KB180
Enable text compression - Potential savings of 22 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js
31 KB21 KB
http://esistem.felcra.com.my/
3 KB2 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://esistem.felcra.com.my/
0 ms714 ms3 KB3 KB200text/htmlDocument
http://esistem.felcra.com.my/flashinglinks.js
727 ms1453 ms2 KB2 KB200application/x-javascriptScript
http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js
728 ms1504 ms32 KB31 KB200application/x-javascriptScript
http://esistem.felcra.com.my/index.gif
728 ms1014 ms37 KB37 KB200image/gifImage
http://esistem.felcra.com.my/pict/today.gif
728 ms1715 ms16 KB16 KB200image/gifImage
Serve static assets with an efficient cache policy - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://esistem.felcra.com.my/index.gif
0 ms37 KB
http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js
0 ms32 KB
http://esistem.felcra.com.my/pict/today.gif
0 ms16 KB
http://esistem.felcra.com.my/flashinglinks.js
0 ms2 KB
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.

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

Remove unused CSS
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.

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 - 2 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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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 720 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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Sistem e-Kenderaan and 3 others render only 6 pixels tall (16 CSS pixels) .

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="ekpi2019/default.asp">Sistem KPI - 2019</a> and 3 others are close to other tap targets .

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

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

Your page has 1 blocking script 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:

http://esistem.felcra.com.my/flashinglinks.js

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://esistem.felcra.com.my/flashinglinks.js (expiration not specified)
http://esistem.felcra.com.my/index.gif (expiration not specified)
http://esistem.felcra.com.my/pict/today.gif (expiration not specified)
http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js (expiration not specified)

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 23.7KiB (65% reduction).

Compressing http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js could save 20.6KiB (65% reduction).
Compressing http://esistem.felcra.com.my/ could save 1.8KiB (66% reduction).
Compressing http://esistem.felcra.com.my/flashinglinks.js could save 1.2KiB (57% reduction).

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 13.1KiB (39% reduction).

Minifying http://esistem.felcra.com.my/wz_tooltip/wz_tooltip.js could save 12.5KiB (40% reduction).
Minifying http://esistem.felcra.com.my/flashinglinks.js could save 646B (30% 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 529B (20% reduction).

Minifying http://esistem.felcra.com.my/ could save 529B (20% reduction).
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.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
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.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does esistem.felcra.com.my use compression?

esistem.felcra.com.my does not use compression.
Original size: 2.68 KB
Compressed size: n/a
File reduced by: n/a

+ 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

esistem.felcra.com.my does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

esistem.felcra.com.my does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Content-Length: 2740
Content-Type: text/html
Content-Location: http://esistem.felcra.com.my/index.htm
Last-Modified: Thu, 07 Mar 2019 08:11:56 GMT
Accept-Ranges: bytes
ETag: "28ca546ebdd4d41:733"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Sun, 22 Mar 2020 03:35:03 GMT

+ DNS Lookup

Type Ip Target TTL
A 103.6.238.212 3600

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

Currently Not Available
Last update was 19 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

virals.ws
4 secs
cpbook.subeen.com
25 secs
paris***s.com
31 secs
***.chatango.com
47 secs
kurk.com.tr
59 secs
goldcoastplants.com.au
1 min
papystream.me
1 min
kurabiyemfincan.com
1 min
app.theother.kitchen
1 min
papstream.xyz
2 mins
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!
esistem.felcra.com.my widget