Refiaprendi - Refiaprendi.web.id

Overview

Snoop Summary for refiaprendi.web.id

This is a free and comprehensive report about refiaprendi.web.id. The domain refiaprendi.web.id is currently hosted on a server located in United States with the IP address 104.18.61.252, where the local currency is USD and English is the local language. Our records indicate that refiaprendi.web.id is owned/operated by Cloudflare, Inc.. Refiaprendi.web.id has the potential to be earning an estimated $1 USD per day from advertising revenue. If refiaprendi.web.id was to be sold it would possibly be worth $950 USD (based on the daily revenue potential of the website over a 24 month period). Refiaprendi.web.id receives an estimated 452 unique visitors every day - a decent amount of traffic! This report was last updated 8th February, 2021.

About refiaprendi.web.id

Site Preview:
Title:
Description:
Keywords and Tags:
Related Terms:
Fav Icon:
Age:	Over 7 years old
Domain Created:	10th May, 2016
Domain Updated:	14th June, 2019
Domain Expires:	10th May, 2020

Review

Snoop Score

1/5

Valuation

$950 USD

Note: All valuation figures are estimates.

Popularity

Low

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	1,931,352
Alexa Reach:	<0.0001%
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority:	0
Moz Page Authority:	0

Rank By Country

Country	Alexa Rank
Indonesia	36,978

Show Rank By Country

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors:	452
Monthly Visitors:	13,757
Yearly Visitors:	164,980

Note: All visitors figures are estimates.

Visitors By Country

Country	Visitors (Unique)	Percentage
Indonesia	Daily: 295 Monthly: 8,984 Yearly: 107,732	65.3%
Other	Daily: 157 Monthly: 4,774 Yearly: 57,248	34.7%

Note: All visitors figures are estimates.

Revenue

Daily Revenue:	$1 USD
Monthly Revenue:	$39 USD
Yearly Revenue:	$470 USD

Note: All revenue figures are estimates.

Revenue By Country

Country	Revenue	Percentage
Indonesia	Daily: $1 USD Monthly: $39 USD Yearly: $470 USD	100%
Other	Daily: $0 USD Monthly: $0 USD Yearly: $0 USD	<0.1%

Note: All revenue figures are estimates.

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	refiaprendi.web.id	18
Domain Name:	refiaprendi	11
Extension (TLD):	webid	5

Expiry Check:

Page Speed Analysis

Average Load Time:	7.44 seconds
Load Time Comparison:	Faster than 3% of sites

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on desktop

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for refiaprendi.web.id. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.5 s
The time taken for the first image or text on the page to be rendered.

First Meaningful Paint — 0.5 s
The time taken for the primary content of the page to be rendered.

Speed Index — 1.1 s
The time taken for the page contents to be visibly populated.

Time to Interactive — 0.5 s
The time taken for the page to become fully interactive.

First CPU Idle — 0.5 s
The time taken for the page's main thread to be quiet enough to handle input.

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive refiaprendi.web.id as laggy when the latency is higher than 0.05 seconds.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Network Requests
Below is a list of network requests that were made during page load.

URL	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://refiaprendi.web.id/	0	562.68300000011	575	0	302	text/html
http://refiaprendi.web.id/cgi-sys/suspendedpage.cgi	563.40600000112	1361.6460000012	4414	7312	200	text/html	Document
http://use.fontawesome.com/releases/v5.0.6/css/all.css	1386.9169999998	1420.986000001	9214	34734	200	text/css	Stylesheet
	1393.7379999988	1393.8310000012	0	3004	200	image/png	Image
http://use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2	1432.9739999994	1462.4960000001	39291	38784	200	application/font-woff2	Font

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
1423.399	17.081
1443.917	5.044
1485.008	23.228
1508.252	8.729
1521.241	6.045

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Refiaprendi.web.id should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Refiaprendi.web.id should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Refiaprendi.web.id should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Refiaprendi.web.id should consider minifying JS files.

Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Refiaprendi.web.id should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Refiaprendi.web.id should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
(Start) http://refiaprendi.web.id/	0
http://refiaprendi.web.id/cgi-sys/suspendedpage.cgi	190

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Refiaprendi.web.id should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 52 KB
Large network payloads can cost users money and are linked to long load times.

URL	Size (Bytes)
http://use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2	39291
http://use.fontawesome.com/releases/v5.0.6/css/all.css	9214
http://refiaprendi.web.id/cgi-sys/suspendedpage.cgi	4414
http://refiaprendi.web.id/	575

Show Details

Uses efficient cache policy on static assets — 0 resources found
Refiaprendi.web.id can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

Avoids an excessive DOM size — 9 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.

Statistic	Element	Value
Total DOM Elements		9
Maximum DOM Depth	SHOW DETAILS	6
Maximum Child Elements	SHOW DETAILS	2

Show Details

Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Refiaprendi.web.id should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
Other	82.114	5.468	1.894

Show Details

Minimizes main-thread work — 0.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Category	Time Spent (Ms)
Other	31.515
Style & Layout	27.152
Rendering	8.992
Parse HTML & CSS	6.57
Script Evaluation	5.468
Script Parsing & Compilation	1.894
Garbage Collection	0.523

Show Details

Keep request counts low and transfer sizes small — 5 requests • 52 KB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	5	53494
Font	1	39291
Stylesheet	1	9214
Document	1	4414
Other	1	575
Image	1	0
Media	0	0
Script	0	0
Third-party	3	48505

Show Details

Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Third-Party	Size (Bytes)	Main-Thread Blocking Time (Ms)
SHOW DETAILS	48505	0

Show Details

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Opportunities

Eliminate render-blocking resources — Potential savings of 140 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Refiaprendi.web.id should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

URL	Size (Bytes)	Potential Savings (Ms)
http://use.fontawesome.com/releases/v5.0.6/css/all.css	9214	120

Show Details

Opportunities

Reduce server response times (TTFB) — Root document took 800 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

URL	Potential Savings (Ms)
http://use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2	29.522000000725

Show Details

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of refiaprendi.web.id. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Refiaprendi.web.id may provide assistance to deaf or hearing-impaired users with captions on audio elements.

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Refiaprendi.web.id may provide assistance to deaf or hearing-impaired users with captions on videos.

`<video>` elements contain a `<track>` element with `[kind="description"]`
Refiaprendi.web.id may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

Show Details

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.

Failing Elements
Account Suspended

Show Details

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.

Failing Elements
html

Show Details

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Failing Elements
meta

Show Details

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.

Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.

Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.

The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.

User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.

Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.

Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.

Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.

Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.

Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.

HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that refiaprendi.web.id should incorporate. This includes practices such as protecting pages with HTTPS.

Passing (13)
Failing (1)

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.

Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.

No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 4 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.

Insecure URL
http://refiaprendi.web.id/
http://refiaprendi.web.id/cgi-sys/suspendedpage.cgi
http://use.fontawesome.com/releases/v5.0.6/css/all.css
http://use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2

Show Details

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for refiaprendi.web.id. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of refiaprendi.web.id on mobile screens.

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.

Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.

Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.

Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

robots.txt is not valid — 118 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Line #	Content	Error
1	<!DOCTYPE html>	Syntax not understood
2	<html>	Syntax not understood
3	<head>	Syntax not understood
4	<meta http-equiv="Content-type" content="text/html; charset=utf-8">	Syntax not understood
5	<meta http-equiv="Cache-control" content="no-cache">	Syntax not understood
6	<meta http-equiv="Pragma" content="no-cache">	Syntax not understood
7	<meta http-equiv="Expires" content="0">	Syntax not understood
8	<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=1">	Syntax not understood
9	<title>Account Suspended</title>	Syntax not understood
10	<link rel="stylesheet" href="//use.fontawesome.com/releases/v5.0.6/css/all.css">	Syntax not understood
11	<style type="text/css">	Syntax not understood
12	body {	Syntax not understood
13	font-family: Arial, Helvetica, sans-serif;	Unknown directive
14	font-size: 14px;	Unknown directive
15	line-height: 1.428571429;	Unknown directive
16	background-color: #ffffff;	Unknown directive
17	color: #2F3230;	Unknown directive
18	padding: 0;	Unknown directive
19	margin: 0;	Unknown directive
20	}	Syntax not understood
21	section {	Syntax not understood
22	display: block;	Unknown directive
23	padding: 0;	Unknown directive
24	margin: 0;	Unknown directive
25	}	Syntax not understood
26	.container {	Syntax not understood
27	margin-left: auto;	Unknown directive
28	margin-right: auto;	Unknown directive
29	padding: 0 10px;	Unknown directive
30	}	Syntax not understood
31	.additional-info {	Syntax not understood
32	background-repeat: no-repeat;	Unknown directive
33	background-color: #293A4A;	Unknown directive
34	color: #FFFFFF;	Unknown directive
35	}	Syntax not understood
36	.additional-info-items {	Syntax not understood
37	padding: 20px;	Unknown directive
38	min-height: 193px;	Unknown directive
39	}	Syntax not understood
40	.info-heading {	Syntax not understood
41	font-weight: bold;	Unknown directive
42	text-align: left;	Unknown directive
43	word-break: break-all;	Unknown directive
44	width: 100%;	Unknown directive
45	}	Syntax not understood
46	.status-reason {	Syntax not understood
47	font-size: 200%;	Unknown directive
48	display: block;	Unknown directive
49	color: #CCCCCC;	Unknown directive
50	}	Syntax not understood
51	.reason-text {	Syntax not understood
52	margin: 20px 0;	Unknown directive
53	font-size: 16px;	Unknown directive
54	}	Syntax not understood
55	.info-heading {	Syntax not understood
56	font-size: 190%;	Unknown directive
57	}	Syntax not understood
58	.reason-text {	Syntax not understood
59	font-size: 140%;	Unknown directive
60	}	Syntax not understood
62	a#dynamicProviderLink, a#dynamicProviderLink:hover, a#dynamicProviderLink:active, a#dynamicProviderLink:visited {	Syntax not understood
63	color: white;	Unknown directive
64	}	Syntax not understood
66	@media (min-width: 768px) {	Unknown directive
67	.additional-info {	Syntax not understood
68	position: relative;	Unknown directive
69	overflow: hidden;	Unknown directive
70	background-image: none;	Unknown directive
71	}	Syntax not understood
72	.additional-info-items {	Syntax not understood
73	padding: 20px;	Unknown directive
74	}	Syntax not understood
75	.container {	Syntax not understood
76	width: 90%;	Unknown directive
77	}	Syntax not understood
78	.status-reason {	Syntax not understood
79	display: inline;	Unknown directive
80	}	Syntax not understood
81	}	Syntax not understood
82	@media (min-width: 992px) {	Unknown directive
83	.additional-info {	Syntax not understood
84	background-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAPAAAADqCAMAAACrxjhdAAAAt1BMVEUAAAAAAAD////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////5+fn////////////////////////////////6+vr///////////////////////////////////////+i5edTAAAAPXRSTlMAAQECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISIjJCUmJygoKSorLC0uLzAwMTIzNDU2Nzg5H7x0XAAACndJREFUeAHtXXlzGs8R7TQ3CFkHxpKxhIwtIBwgIuYY4u//uVJ2qpLKD7Q8t2Z7xpD3n6ska9/2bM9Mvz6oGEyXFoKHfmheoewx9cYehVuPHMT4jphyBtNHxHQmDGgBvZjXBuWN2gogbPy6RtcOejNPxFkb+CEYhHCfmJ6DQShfEGfMt71FOPgpE1PHOMTEY8oZ3yCr2UtiInqEftj3iLM18Afsu/xKv9B4QUzsV1XKFTzDPG+LfoLpE/LjJnzO08QCAugLalKeqP/mEmW6Qj+BPIE7IYmTyw1MFwbaksaybSxDCA4STF+wg8rH7EzMwqNibY38mlvXKDdU5pDH3TRkl40vxJkZ+DO2Nu/3HnyC7t15obGBtqRFRXo6+0Z5YQh5LHd9YGWOsF+9Is5oQXctZKbvdAAtbHHM8+GLfojWdIgPff7YifRTNiZmusW+w8fDj1xdevNnbU3VFfTEL/W33pfH31cGYBpgW9Lba3Ic8C8iA77NLe514vu8BPj6/n3lCd/VkgKXGkwYUQHAaM+yQunBmNSwbRVYh+kOcgMhvRDB1Md20YfiR+UFfvdIizp2v1vVjt0usa1pmNzAX2IFl5/xaE9aqQGSD6bxI0RZSw3uuF0YjQHepjMxHmd9IgC1NbY1VSkdeB4vXMH0KSQVIvQfERciMpcaFtW4H8iI0gB2MzfEcV3gB+IkfDtbyCATgtHB7l3TrKUG2yWOe7O2KYQIPE7xFD12Yvy6SvqoLOMf95k+BvgqogCFCx22NdltO1epYc7ycEKSaI9+UAYPGOlKDQYyxDP9Npqv0NKZkS7GuNRQig5pvaYQwdTztjRnCrr/l0b2UgO+wRtMiFCAzqpLL0So+hWmi61Nn3aqKGEzDfFrmEoKqcWSFDRONSrAU0iFYLrHU2RKB3q+HxDHT4JKEe2prhxY1aCS5lY+HnXu6N+x6IJCRQQmEEz+YjIE/xs/MmD8qHRYK5CAHuaTY5jfQxFC/YoIQSSVafrD+WK4H0Piv8SATRZChEXiOs39L/IYwiOxRHgeEKcmbMI9ccHRCdxUeYanFpQJMBUDIFxw1chJiBAomkz3x43l+nuWGmWhkQs0a6Y7YHVe772m1tZlUBEhKI9k6nuLE8bzKVSECEHeCZSysr04qJGnTzsVxJoQwm7bPhQ7cza5ECGQGpg6TnjzmWBbU7tExkhVw36yz3HCm0qEvEZ9C7vDYZeWAQhnKkQUG/i7NDnCL/hwbvJr6miPKHTaOE54xpBGrl8RIXKX1bk3+A1aUhHxUte3sHEvNSIp4REdBNONA9NOWYEwuq54AhPex3NaIQLwHIIQlQkPbwsRFpdmdb/hD8TSDCwTBu8W30sSIiS7P9NwZ7CgAeDjlaM9ktAD0+Mxwrse8XsTaMoRIoCaZmg3BQgLqrHVCBu3qhW3+AAOhwp52QIAfQkAwoDHKzfNEYck4ZPp5qh5Cp4VFiL8WM/Cl8SF4pgthvtHm4qQUIiQdY+5NMfu/228Pkq3NZNMqD1W7rMnrwJeQEmIwKsacMI/TVOLlHjQjM1YVtVQ3RwhvORo3ckiQ5ZOUzlCOMyi9Z+LXREhS5iqrI4QnuNlf8oVEbK8A556QQK0LNrTj2tiWfcFnh0hPIpYEVGjmBAe2b95U3wMxioiErRm2nuhd8QRCA8IwTRAW1O7PAsbtCPyMMgJp+1/IaxqGARzrFttphUR+MvEPSx+6m/pCxEi3Y7p485ESAVmuldvzSTKw2fqHSGM5hBW1IUI0f/LdONtEUKXGC95jK+Rg4QBVwNmlePZVjTxuo24kWMrQHg/nZzxDqmqFRFC799+dbEirMoVEXhVA07Y+GWNMOBCxIIpCgCpAX5KgHB6IQILHwE3HXk2XQVszdSkGECjUABhPLMdT/uKL0RIQ8DzYOKJu98V006LbSIkvBsRlzBPYkIRIH1743iEielBT4iQRkNHwUQMUtTWXqsiQugBiwl73OOrV0RIq/6+BIPPVVLrbAVAulQKIwAO/9jUKyJk51SmO5wwhpHXac0E3EQEfRIu6TfBYLQn/J3eCcFdE7i4dwmHckWErJsmU7eIsGnLxpVpVETI4kVM3VCUw1+XdRPRaM0k64jL1LEFkBBGRw7ad1ZE+AVH74Xh8NQM/dZMxVKDkPCyWmbPJ/8uIQJ/XbiL8bNKvv0vWlLCb0fQjR9zuU1y+sSkjcqsgPAzCVGFWzPpYxJM9GAMXhGRinD85xkrCxEomEY7I7j/40IEvjWlJ7wDzjJZtmbCW/cChOPPtlICMGXIAX3QFYQIRcI3Cq2ZNk3tYduunPxIpus8JoLi5e1u2yWN1kxd3UV9VXAdvnjntIksh1V3BSe/DIUIHBdRCMMV6OnHrtW3bxc8VJVmPQ+IFQmbtyUgejem6VszwaNJ5IQT9r8AUF04/DoMI+Nh1ZW5M4chJ5yuNRMAnv7Th0PwP74pTl9UjPZ8Gj19PYSn0S1FQG2VfGvSPqxrp52mBN6I25n2CTBOORE0/6GiVn9YNf8bFBd4RURFlWzBvyBEqIi4I9aky+2r29597/ZD62+xKVfBtNM6qaHRG61erXPBOfO6HN7UYlJmuslpWDUTdYab4L2z1v40hPPBvwzqOluTvhDBVB2a4Iyx/4UxLrx8goycW0UEgO4y2L3H+Ul5XI/4voc6rZkA3Bpv3njfS/nhR781E54N6t4OeWxQxuknguJ1S84ARR4RwAqtmaCFZnRiL2lbM+HaAC5npq+IwF+6hhfBWzNNlW6qCrGXRyza0yNOd1E1fsYUC7UV2Jop7XyXbsw90KYUInjpkRcecWfkEmdCAehgueuTmNt+shkReKd3v67nP9cNDJHvoD++xdvpovXKCp5SfoGxHsj0yF+IwHUus7smVh8IHVGIwJtLy7uN6Pe/wAnrBxOnAayISLWkQ8woBKyR++dUTsuEK+L8p2BD4fGdsfqhxGQTQZluHULXrRsUFfBE0OgzIlraR8vkw6qnXmuDSF8RgS8th+d+phci8FJf1fwapi44rFpfqTZAnW+JFRG3kf94Z+sSqdR1UIiI/dc/B6N/M9WsiADO00A3QU0hohX5RTdeCrstyT1WphURTBevBaV4iwYJGGctRDC1FsGaQ3RtGFfL4os34g6T+AkAT84bs0fX2weS88X7X6hXRDDRzdwHZ/5D2hjjght3Mb5y1NINq+beZBu8d84657wPYfN8pZBc0g+JKiKYiNr9r4v1Zrvdbtazp16TSCOfZppMiGD6iVqr271oVokU6AJ9U5FGnXIww5mH+kLEhxI1cl20QCGCTgRMA/3+F2lRXXtzXhURPTTt9GQA6h+d/1dE5An9GRH5o5mwIgKHvhCBi5j60Bci8oe+EKEPrYmg+QNNOw3PdCLgpBUROPQ18mX1ZEx8p9//Ii0qc3Qi6CmAU1dEpD9SA1tT98/GZadvf29GxPYPh9n+MjAuRNg/Hc4WYm8WjT0pABNB7WkAb81kz8fEo5Na0rAQYU8KQEWEPSkAaafnRPiXEGHPCCbcnxphIEPPnhXc9XkRNuHh3Cw8JXteeCV7Zjg/wua8YGl3XvDUPy/c/Avd4/hNDSqegQAAAABJRU5ErkJggg==);	Unknown directive
85	}	Syntax not understood
86	.container {	Syntax not understood
87	width: 70%;	Unknown directive
88	}	Syntax not understood
89	.status-reason {	Syntax not understood
90	font-size: 450%;	Unknown directive
91	}	Syntax not understood
92	.info-heading {	Syntax not understood
93	font-size: 200%;	Unknown directive
94	}	Syntax not understood
95	.reason-text {	Syntax not understood
96	font-size: 160%;	Unknown directive
97	}	Syntax not understood
98	}	Syntax not understood
99	</style>	Syntax not understood
100	</head>	Syntax not understood
101	<body>	Syntax not understood
102	<div class="container">	Syntax not understood
103	<span class="status-reason">	Syntax not understood
104	<i class="fas fa-user-times fa-2x"></i> Account Suspended	Syntax not understood
105	</span>	Syntax not understood
106	</div>	Syntax not understood
107	<section class="additional-info">	Syntax not understood
108	<div class="container">	Syntax not understood
109	<div class="additional-info-items">	Syntax not understood
110	<div class="info-heading">	Syntax not understood
111	This Account has been suspended.	Syntax not understood
112	</div>	Syntax not understood
113	<div class="reason-text">	Syntax not understood
114	<a href="https://idcloudhost.com" id="dynamicProviderLink" title="PT Cloud Hosting Indonesia" rel="noopener noreferrer">Contact your hosting provider</a> for more information.	Unknown directive
115	</div>	Syntax not understood
116	</div>	Syntax not understood
117	</div>	Syntax not understood
118	</section>	Syntax not understood
119	</body>	Syntax not understood
120	</html>	Syntax not understood

Show Details

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of refiaprendi.web.id. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of refiaprendi.web.id on mobile screens.

Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.

`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 4 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.

Insecure URL
http://refiaprendi.web.id/
http://refiaprendi.web.id/cgi-sys/suspendedpage.cgi
http://use.fontawesome.com/releases/v5.0.6/css/all.css
http://use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2

Show Details

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.

Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data

Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.

Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.

Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on mobile

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for refiaprendi.web.id. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 1.4 s
The time taken for the first image or text on the page to be rendered.

First Meaningful Paint — 1.4 s
The time taken for the primary content of the page to be rendered.

Time to Interactive — 1.4 s
The time taken for the page to become fully interactive.

First CPU Idle — 1.4 s
The time taken for the page's main thread to be quiet enough to handle input.

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive refiaprendi.web.id as laggy when the latency is higher than 0.05 seconds.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Network Requests
Below is a list of network requests that were made during page load.

URL	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://refiaprendi.web.id/	0	478.55999995954	579	0	302	text/html
http://refiaprendi.web.id/cgi-sys/suspendedpage.cgi	479.00499997195	1967.2479999717	4414	7312	200	text/html	Document
http://use.fontawesome.com/releases/v5.0.6/css/all.css	1979.4720000355	2010.8169999439	9214	34734	200	text/css	Stylesheet
http://use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2	2016.9699999969	2046.7189999763	39291	38784	200	application/font-woff2	Font

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
1991.22	7.499
2035.836	8.82

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

First Contentful Paint (3G) — 2790 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.