Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

infid.org

INFID

Page Load Speed

63.7 sec in total

First Response

9.9 sec

Resources Loaded

52.9 sec

Page Rendered

800 ms

infid.org screenshot

About Website

Visit infid.org now to see the best up-to-date INFID content for Indonesia and also check out these interesting facts you probably never knew about infid.org

Visit infid.org

Key Findings

We analyzed Infid.org page load time and found that the first response time was 9.9 sec and then it took 53.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 10 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

infid.org performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value21.0 s

0/100

10%

TBT (Total Blocking Time)

Value9,880 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value31.4 s

0/100

10%

Network Requests Diagram

infid.org

9948 ms

language-selector.css

658 ms

styles.css

627 ms

settings.css

1719 ms

css

84 ms

Our browser made a total of 295 requests to load all elements on the main page. We found that 34% of them (99 requests) were addressed to the original Infid.org, 13% (39 requests) were made to Scontent.xx.fbcdn.net and 10% (30 requests) were made to Andreas-bkh.net. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Infid.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (41%)

Content Size

5.6 MB

After Optimization

3.3 MB

In fact, the total size of Infid.org main page is 5.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 143.3 kB

  • Original 167.4 kB
  • After minification 139.4 kB
  • After compression 24.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 28.0 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 143.3 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 169.1 kB

  • Original 3.0 MB
  • After minification 2.8 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. INFID images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 864.7 kB

  • Original 1.2 MB
  • After minification 1.0 MB
  • After compression 335.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 864.7 kB or 72% of the original size.

CSS Optimization

-89%

Potential reduce by 1.1 MB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 130.8 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Infid.org needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 152 (56%)

Requests Now

272

After Optimization

120

The browser has sent 272 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INFID. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 86 to 1 for JavaScripts and from 43 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

infid.org accessibility score

52

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

infid.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

infid.org SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ID

  • Language Claimed

    ID

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Infid.org can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it matches the claimed language. Our system also found out that Infid.org main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of INFID. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: