Kontan.co.id - SEO Checker

Your Website Score is

Similar Ranking

BERITA TERKINI INVESTASI DAN EKONOMI INDONESIA - KONTAN

kontan.co.id

BLOG TOOL, PUBLISHING PLATFORM, AND CMS &MDASH; WORDPRESS.ORG

s.w.org

NEW ATLAS - NEW TECHNOLOGY & SCIENCE NEWS

newatlas.com

WEBSITE TRAFFIC STATISTICS & ANALYTICS - SIMILARWEB

similarweb.com

WHOIS.COM - DOMAIN NAMES & IDENTITY FOR EVERYONE

whois.com

STAR TREK (OFFICIAL SITE)

startrek.com

THE OPEN WEB'S DISCOVERY & NATIVE ADVERTISING FEED | OUTBRAIN.COM

outbrain.com

Latest Sites

CLOUD HOSTING MURAH RINTISHOSTING

rintishosting.com

GUDANG INFORMASI TEKNOLOGI

cilup.com

BEST CAM GIRLS- FREE --- CHAT

liveamor.com

HOME - TOP10HOSTED

top10hosted.com

WATCH LIVE CAMS NOW! NO REGISTRATION REQUIRED - 100% FREE UNCENSORED!

livesusan.com

MIHENTAI - READ HENTAI MANGA ONLINE VIA MOBILE

mihentai.com

0NI0N.NINJA

0ni0n.ninja

Top Technologies

PHP

Programming Languages

Google Font API

Font Scripts

WordPress

CMS

CloudFlare

CDN

jQuery

JavaScript Frameworks

Nginx

Web Servers

Font Awesome

Font Scripts

Google Tag Manager

Tag Managers

Apache

Web Servers

LiteSpeed

Web Servers

72 kontan.co.id Last Updated: 7 months

Success 62% of passed verification steps

Warning 15% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 51%

Best Practices Desktop Score 57%

SEO Desktop Score 80%

Progressive Web App Desktop Score 26%

Performance Mobile Score 10%

Best Practices Mobile Score 57%

SEO Mobile Score 82%

Progressive Web App Mobile Score 29%

Page Authority Authority 53%

Domain Authority Domain Authority 61%

Moz Rank 5.3/10

Bounce Rate Rate 0%

charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 55 Characters

BERITA TERKINI INVESTASI DAN EKONOMI INDONESIA - KONTAN

Meta Description 109 Characters

Berita terbaru Investasi, Nasional, Industri, Peluang Usaha, Keuangan, Internasional, Data pasar dan Ekonomi.

Effective URL 28 Characters

https://www.kontan.co.id:443

Excerpt Page content

Keywords Cloud Density

lalu20 menit19 saham15 ihsg12 internasional10 kontan10 hari9 bisa9 investasi9 industri9

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
lalu	20
menit	19
saham	15
ihsg	12
internasional	10
kontan	10
hari	9
bisa	9
investasi	9
industri	9

Google Preview Your look like this in google search result

BERITA TERKINI INVESTASI DAN EKONOMI INDONESIA - KONTAN

https://www.kontan.co.id:443

Berita terbaru Investasi, Nasional, Industri, Peluang Usaha, Keuangan, Internasional, Data pasar dan Ekonomi.

Robots.txt File No Found

http://kontan.co.id/robots.txt

Sitemap.xml File Detected

http://kontan.co.id/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~94.84 KB

Code Size: ~78.5 KB

Text Size: ~16.34 KB Ratio: 17.22%

Social Data

Estimation Traffic and Earnings

444,522

Unique Visits

Daily

822,365

Pages Views

Daily

$1,588

Income

Daily

12,446,616

Unique Visits

Monthly

23,437,403

Pages Views

Monthly

$39,700

Income

Monthly

144,025,128

Unique Visits

Yearly

276,314,640

Pages Views

Yearly

$419,232

Income

Yearly

Technologies

PWA - Manifest

Manifest is not valid

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

Desktop

Enable text compression Potential savings of 388 KiB

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

Speed Index 3.3 s

Speed Index shows how quickly the contents of a page are visibly populated

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

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

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

First CPU Idle 6.7 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/).

Preload key requests Potential savings of 350 ms

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

First Contentful Paint 1.0 s

First Contentful Paint marks the time at which the first text or image is painted

Estimated Input Latency 40 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

Includes front-end JavaScript libraries with known security vulnerabilities 3 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Serve static assets with an efficient cache policy 58 resources found

A long cache lifetime can speed up repeat visits to your page

Largest Contentful Paint element 1 element found

This is the largest contentful element painted within the viewport

Remove duplicate modules in JavaScript bundles Potential savings of 9 KiB

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Reduce JavaScript execution time 3.0 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Max Potential First Input Delay 190 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task

Avoid an excessive DOM size 1,399 elements

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

Avoid serving legacy JavaScript to modern browsers Potential savings of 64 KiB

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers

Serve images in next-gen formats Potential savings of 134 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

Total Blocking Time 270 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

Time to Interactive 5.9 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Avoid long main-thread tasks 6 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

Remove unused JavaScript Potential savings of 409 KiB

Remove unused JavaScript to reduce bytes consumed by network activity

Properly size images Potential savings of 188 KiB

Serve images that are appropriately-sized to save cellular data and improve load time

Reduce initial server response time Root document took 1,230 ms

Keep the server response time for the main document short because all other requests depend on it

Avoid chaining critical requests 40 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

Keep request counts low and transfer sizes small 660 requests • 3,792 KiB

To set budgets for the quantity and size of page resources, add a budget.json file

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 36.3 s

A fast page load over a cellular network ensures a good mobile user experience

Minimize main-thread work 5.2 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

Minify CSS Potential savings of 4 KiB

Minifying CSS files can reduce network payload sizes

Cumulative Layout Shift 0.442

Cumulative Layout Shift measures the movement of visible elements within the viewport

Defer offscreen images Potential savings of 29 KiB

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

Avoid large layout shifts 5 elements found

These DOM elements contribute most to the CLS of the page.

Avoid enormous network payloads Total size was 3,792 KiB

Large network payloads cost users real money and are highly correlated with long load times

Minimize third-party usage Third-party code blocked the main thread for 240 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

First Meaningful Paint 1.1 s

First Meaningful Paint measures when the primary content of a page is visible

Eliminate render-blocking resources Potential savings of 760 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

User Timing marks and measures 48 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Largest Contentful Paint 2.3 s

Largest Contentful Paint marks the time at which the largest text or image is painted

Efficiently encode images Potential savings of 34 KiB

Optimized images load faster and consume less cellular data

Mobile

Enable text compression Potential savings of 200 KiB

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

Total Blocking Time 1,670 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

First Contentful Paint 4.0 s

First Contentful Paint marks the time at which the first text or image is painted

Cumulative Layout Shift 0.601

Cumulative Layout Shift measures the movement of visible elements within the viewport

Avoid an excessive DOM size 839 elements

Properly size images Potential savings of 51 KiB

Serve images that are appropriately-sized to save cellular data and improve load time

Reduce the impact of third-party code Third-party code blocked the main thread for 1,000 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 serving legacy JavaScript to modern browsers Potential savings of 52 KiB

Avoid chaining critical requests 22 chains found

Avoid large layout shifts 5 elements found

These DOM elements contribute most to the CLS of the page.

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Reduce initial server response time Root document took 1,160 ms

Keep the server response time for the main document short because all other requests depend on it

Avoid enormous network payloads Total size was 2,849 KiB

Large network payloads cost users real money and are highly correlated with long load times

Keep request counts low and transfer sizes small 365 requests • 2,849 KiB

To set budgets for the quantity and size of page resources, add a budget.json file

First Meaningful Paint 4.1 s

First Meaningful Paint measures when the primary content of a page is visible

First Contentful Paint (3G) 8790 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Efficiently encode images Potential savings of 131 KiB

Optimized images load faster and consume less cellular data

Time to Interactive 26.0 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Document uses legible font sizes 99.24% 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

Remove unused JavaScript Potential savings of 263 KiB

Remove unused JavaScript to reduce 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

Serve images in next-gen formats Potential savings of 221 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

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

Minimize main-thread work 11.4 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

Remove unused CSS Potential savings of 55 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

Preload key requests Potential savings of 1,650 ms

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

Largest Contentful Paint element 1 element found

This is the largest contentful element painted within the viewport

Avoid long main-thread tasks 20 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

Page load is not fast enough on mobile networks Interactive at 26.0 s

A fast page load over a cellular network ensures a good mobile user experience

Remove duplicate modules in JavaScript bundles Potential savings of 10 KiB

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Max Potential First Input Delay 380 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task

Reduce JavaScript execution time 6.3 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Largest Contentful Paint 11.2 s

Largest Contentful Paint marks the time at which the largest text or image is painted

Estimated Input Latency 80 ms

Eliminate render-blocking resources Potential savings of 2,980 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

First CPU Idle 19.0 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/).

Speed Index 13.4 s

Speed Index shows how quickly the contents of a page are visibly populated

Includes front-end JavaScript libraries with known security vulnerabilities 8 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Serve static assets with an efficient cache policy 44 resources found

A long cache lifetime can speed up repeat visits to your page

Defer offscreen images Potential savings of 92 KiB

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

User Timing marks and measures 32 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Tap targets are not sized appropriately 97% 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

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you

Title Website

Congratulations! Your title is optimized

Description Website

Congratulations! Your description is optimized

Robots.txt

Warning! Your site not 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

Warning! Your site have errors W3C

Accelerated Mobile Pages (AMP)

Congratulations! Your site have AMP Version

Domain Authority

Congratulations! Your Domain Authority is good

GZIP Compress

Warning! Your site not is compressed, this can make slower response for the visitors

Favicon

Congratulations! Your website appears to have a favicon.

Broken Links

Warning! You have broken links View links

First 20 Links	Relationship	HTTP Status
Edit Profil	Internal Link	301
Ganti Password	Internal Link	301
Keluar	Internal Link	301
Epaper	Internal Link	200
KSTORE	Internal Link	0
PRESSRELEASE.ID	Internal Link	200
KINERJAEMITEN.COM	Internal Link	200
ADVERTISING	Internal Link	0
Login	Internal Link	301
Daftar	Internal Link	301
http://www.kontan.co.id	Internal Link	301
http://epaper.kontan.co.id/cetak	Internal Link	301
insight	Internal Link	301
Investasi	Internal Link	301
Keuangan	Internal Link	301
Industri	Internal Link	301
Nasional	Internal Link	301
Internasional	Internal Link	301
Personal Finance	Internal Link	301
Lifestyle	Internal Link	301

Alexa Rank

852

Global Rank

35

Indonesia

Traffic

Search

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/2 200 
date: Thu, 24 Sep 2020 07:03:06 GMT
content-type: text/html; charset=UTF-8
server: nginx
vary: Accept-Encoding
x-powered-by: PHP/7.3.7
set-cookie: life_session=a%3A5%3A%7Bs%3A10%3A%22session_id%22%3Bs%3A32%3A%2216d544d353305ec06d5d03879609dab6%22%3Bs%3A10%3A%22ip_address%22%3Bs%3A12%3A%22172.16.21.64%22%3Bs%3A10%3A%22user_agent%22%3Bs%3A20%3A%22Chrome+85.0.4183.102%22%3Bs%3A13%3A%22last_activity%22%3Bi%3A1600930986%3Bs%3A9%3A%22user_data%22%3Bs%3A0%3A%22%22%3B%7Df16022dc4ba40ca905007bd6ee6830565cd3aa8e; expires=Thu, 24-Sep-2020 09:03:06 GMT; Max-Age=7200; path=/
set-cookie: life_session=a%3A0%3A%7B%7D; expires=Wed, 25-Sep-2019 17:03:06 GMT; Max-Age=0; path=/
set-cookie: life_session=a%3A0%3A%7B%7D; expires=Wed, 25-Sep-2019 17:03:06 GMT; Max-Age=0; path=/
content-encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	kontan.co.id	52.77.58.176	IN	58
A	kontan.co.id	3.0.165.182	IN	58
NS	kontan.co.id	ns-1043.awsdns-02.org	IN	172800
NS	kontan.co.id	ns-1932.awsdns-49.co.uk	IN	172800
NS	kontan.co.id	ns-322.awsdns-40.com	IN	172800
NS	kontan.co.id	ns-612.awsdns-12.net	IN	172800
MX	kontan.co.id	relayhost.dutaint.com	IN	300
MX	kontan.co.id	mx1.kontan.co.id	IN	300
TXT	kontan.co.id	v=spf1 a mx include:dutaservisindo.co.id ~all	IN	300

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

72 kontan.co.id Last Updated: 7 months

Desktop

Mobile

Social Data

Estimation Traffic and Earnings

Technologies

Font Awesome

Google Tag Manager

jQuery

Nginx

PHP

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Alexa Rank

852

35

Information Server

Comments

About Us

Contact Info

Follow Us