Your Website Score is

Similar Ranking

29
PEMERINTAH GAMPONG KEUDE BLANG JRUEN, LAKUKAN SOSIALISASI RANCANGAN QANUN GAMPONG, INI YANG DI HARAPKAN
nanggroe.net
29
404 NOT FOUND
youwatch.pro
29
ACEHTREND.COM - BERITA DARI ACEH & OPINI INSPIRATIF
acehtrend.com
29
TÀI KHOẢN GOOGLE DRIVE UNLIMITED 2020 - GOOGLE DRIVE KHÔNG GIỚI HẠN
gdrive.vip
29
MONITORING ALL SERVER
status.adlk.us
29
LAGARE.MA - البوابة الإلكترونية للمحطة الطرقية
lagare.ma
29
FILEHIPPO - SITUS TEKNOLOGI DOWNLOAD GAME MOD APK & APPS
filehippo.co.id

Latest Sites

34
PLAY CASINO ONLINE - BIGGEST & HAPPIEST CASINO IN ASIA - HAPPY LUKE
beritabola89.com
19
HEALTY99 - PANDUAN SEHAT SECARA ALAMI
healty99.com
17
شات مصر: شات كتابي للجوال
chatnt.com
55
TEDI EKA • LEARN, FOR SHARE
tedieka.com
41
DEKAT.PAGE
dekat.page
39
TAXI 216 - UNE APPLICATION 100% TUNISIEN
taxi216.dev.anypli.com
45
THECUY - SEPUTAR KESEHATAN, SEPUTAR TEKNOLOGI & BERBAGAI TIPS
thecuy.com

Top Technologies

Google Font API
Font Scripts
WordPress
CMS
CloudFlare
CDN
Nginx
Web Servers
Font Awesome
Font Scripts
Google Tag Manager
Tag Managers
Apache
Web Servers
Twitter Bootstrap
Web Frameworks

29 identifai.id Last Updated: 2 months

Success 55% of passed verification steps
Warning 38% of total warning
Errors 7% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 83%
Best Practices Desktop Score 86%
SEO Desktop Score 100%
Progressive Web App Desktop Score 30%
Performance Mobile Score 38%
Best Practices Mobile Score 86%
SEO Mobile Score 97%
Progressive Web App Mobile Score 32%
Page Authority Authority 9%
Domain Authority Domain Authority 11%
Moz Rank 0.9/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 78 Characters
IDENTIFAI | E-KYC VALIDATION & VERIFICATION SOFTWARE SOLUTION IN INDONESIA
Meta Description 273 Characters
We deliver EKYC online software solution through customer face recognation, identification, validation & verification process by utilizing the AI-based technology system such as Dukcapil registration ,Identity card creation and for all businesses in Jakarta, Indonesia.
Effective URL 24 Characters
https://www.identifai.id
Excerpt Page content
IdentifAI | E-KYC Validation & Verification Software Solution in Indonesia Your Solution Sheet Will be ReadyNameEmail AddressCOmpanyThank you! Your submission has been received!Oops! Something went wrong while submitting the form.OUR SOLUTIO...
Keywords Cloud Density
face18 data16 dukcapil15 process11 platform9 identifai9 customer8 nodeflux8 validation7 ekyc7
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
face 18
data 16
dukcapil 15
process 11
platform 9
identifai 9
customer 8
nodeflux 8
validation 7
ekyc 7
Google Preview Your look like this in google search result
IDENTIFAI | E-KYC VALIDATION & VERIFICATION SOFTWARE SOL
https://www.identifai.id
We deliver EKYC online software solution through customer face recognation, identification, validation & verification process by utilizing the AI-
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~27.18 KB
Code Size: ~20.42 KB
Text Size: ~6.77 KB Ratio: 24.90%

Social Data

Delicious Total: 0
Facebook Total: 2
Google Total: 0
Linkedin Total: 0
Pinterest Total: 0
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

Estimation Traffic and Earnings

80
Unique Visits
Daily
148
Pages Views
Daily
$0
Income
Daily
2,240
Unique Visits
Monthly
4,218
Pages Views
Monthly
$0
Income
Monthly
25,920
Unique Visits
Yearly
49,728
Pages Views
Yearly
$0
Income
Yearly

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Max Potential First Input Delay 150 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids an excessive DOM size 313 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)
Serve static assets with an efficient cache policy 7 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid enormous network payloads Total size was 6,505 KiB
Large network payloads cost users real money and are highly correlated with long load times
User Timing marks and measures 5 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
First CPU Idle 2.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Minimize third-party usage Third-party code blocked the main thread for 20 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Avoid chaining critical requests 39 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
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Eliminate render-blocking resources Potential savings of 250 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Remove unused JavaScript Potential savings of 180 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoid serving legacy JavaScript to modern browsers Potential savings of 14 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
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
Efficiently encode images Potential savings of 91 KiB
Optimized images load faster and consume less cellular data
Remove duplicate modules in JavaScript bundles Potential savings of 17 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Properly size images Potential savings of 240 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 13.3 s
A fast page load over a cellular network ensures a good mobile user experience
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 16 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Estimated Input Latency 20 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Minimizes main-thread work 1.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 2.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
JavaScript execution time 0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index 1.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Keep request counts low and transfer sizes small 104 requests • 6,505 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Initial server response time was short Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it
Cumulative Layout Shift 0.09
Cumulative Layout Shift measures the movement of visible elements within the viewport
Total Blocking Time 60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve images in next-gen formats Potential savings of 509 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Mobile

Mobile Screenshot
Initial server response time was short Root document took 230 ms
Keep the server response time for the main document short because all other requests depend on it
First Meaningful Paint 2.0 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint 2.0 s
First Contentful Paint marks the time at which the first text or image is painted
First CPU Idle 5.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Serve images in next-gen formats Potential savings of 495 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Cumulative Layout Shift 0.147
Cumulative Layout Shift measures the movement of visible elements within the viewport
Remove unused CSS Potential savings of 15 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
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
Page load is not fast enough on mobile networks Interactive at 12.6 s
A fast page load over a cellular network ensures a good mobile user experience
Properly size images Potential savings of 115 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Tap targets are not sized appropriately 70% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Avoid long main-thread tasks 16 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Eliminate render-blocking resources Potential savings of 630 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Document uses legible font sizes 62.55% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoids an excessive DOM size 313 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)
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Reduce JavaScript execution time 2.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Remove unused JavaScript Potential savings of 180 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Max Potential First Input Delay 670 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minimize third-party usage Third-party code blocked the main thread for 200 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
User Timing marks and measures 5 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Speed Index 4.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Keep request counts low and transfer sizes small 99 requests • 6,680 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint 8.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Time to Interactive 12.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid serving legacy JavaScript to modern browsers Potential savings of 14 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Remove duplicate modules in JavaScript bundles Potential savings of 15 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes
Avoid enormous network payloads Total size was 6,680 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve static assets with an efficient cache policy 6 resources found
A long cache lifetime can speed up repeat visits to your page
Estimated Input Latency 180 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
Efficiently encode images Potential savings of 91 KiB
Optimized images load faster and consume less cellular data
Total Blocking Time 900 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid chaining critical requests 39 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
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
Minimize main-thread work 5.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint (3G) 4125 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Warning! Your title is not optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Congratulations! Your site not have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

4,516,755

Global Rank

4,516,755

Global
Traffic
Search

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
server: openresty
date: Fri, 27 Nov 2020 07:20:09 GMT
content-type: text/html
content-length: 8557
content-encoding: gzip
via: 1.1 varnish, 1.1 varnish
accept-ranges: bytes
age: 99
x-served-by: cache-dca17762-DCA, cache-sea4423-SEA
x-cache: HIT, HIT
x-cache-hits: 1, 1
x-timer: S1606461609.184808,VS0,VE1
vary: Accept-Encoding
x-cluster-name: us-west-2-prod-eks-15
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments