Tools & Wizards About Us

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

brilio.net

Young, Fun, & Creative - Brilio.net

Page Load Speed

10.1 sec in total

First Response

398 ms

Resources Loaded

8.2 sec

Page Rendered

1.5 sec

About Website

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

Temukan segala kisah kehidupan, gaya hidup, renungan, inspirasi, dan ilmu pengetahuan di sini

Visit brilio.net

Key Findings

We analyzed Brilio.net page load time and found that the first response time was 398 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

brilio.net performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value17.7 s

0/100

10%

TBT (Total Blocking Time)

Value9,260 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value37.4 s

0/100

10%

Network Requests Diagram

brilio.net

398 ms

www.brilio.net

533 ms

swiper@10.min.css

95 ms

font-awesome@4.min.css

78 ms

app.1c8b6ebc1a683ac85be7.css

95 ms

Our browser made a total of 169 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Brilio.net, 65% (110 requests) were made to Cdn-brilio-net.akamaized.net and 4% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Cdn-brilio-net.akamaized.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 777.3 kB (36%)

Content Size

2.2 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brilio.net main page is 2.2 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. Javascripts take 859.2 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 491.5 kB

  • Original 539.6 kB
  • After minification 390.5 kB
  • After compression 48.1 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 149.1 kB, which is 28% 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 491.5 kB or 91% of the original size.

Image Optimization

-18%

Potential reduce by 137.3 kB

  • Original 772.7 kB
  • After minification 635.5 kB

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. Obviously, Brilio needs image optimization as it can save up to 137.3 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 148.6 kB

  • Original 859.2 kB
  • After minification 813.9 kB
  • After compression 710.6 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 148.6 kB or 17% of the original size.

CSS Optimization

-0%

Potential reduce by 11 B

  • Original 8.5 kB
  • After minification 8.5 kB
  • After compression 8.5 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. Brilio.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 79 (51%)

Requests Now

154

After Optimization

75

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

brilio.net accessibility score

89

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

button, link, and menuitem elements do not have accessible names.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

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

Best Practices

brilio.net best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

brilio.net SEO score

83

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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 Brilio.net 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 Brilio.net 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 data is detected on the main page of Brilio. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: