Tools & Wizards About Us
onblr.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

onblr.com

온블러

Page Load Speed

6.7 sec in total

First Response

973 ms

Resources Loaded

5.5 sec

Page Rendered

243 ms

onblr.com screenshot

About Website

Click here to check amazing Onblr content. Otherwise, check out these important facts you probably never knew about onblr.com

카드, 은행, 증권, 보험, 부동산 통합관리,잔액이 자동으로 이월되는 복식부기 가계부서비스.

Visit onblr.com

Key Findings

We analyzed Onblr.com page load time and found that the first response time was 973 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

onblr.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value470 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

onblr.com

973 ms

cometchatcss.php

433 ms

cometchatjs.php

1307 ms

f091e643820c909a17b3401ee32a75c2.css

2147 ms

resolution.css

1084 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that all of those requests were addressed to Onblr.com and no external sources were called. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Onblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 627.7 kB (51%)

Content Size

1.2 MB

After Optimization

600.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onblr.com main page is 1.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. Only 10% of websites need less resources to load. Javascripts take 485.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 19.0 kB

  • Original 25.8 kB
  • After minification 24.5 kB
  • After compression 6.8 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 19.0 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 9.8 kB

  • Original 432.0 kB
  • After minification 422.3 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. Onblr images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 355.7 kB

  • Original 485.3 kB
  • After minification 483.0 kB
  • After compression 129.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 355.7 kB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 243.3 kB

  • Original 284.6 kB
  • After minification 243.6 kB
  • After compression 41.3 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. Onblr.com needs all CSS files to be minified and compressed as it can save up to 243.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (52%)

Requests Now

21

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onblr.com

onblr.com

973 ms

cometchatcss.php

cometchatcss.php

433 ms

cometchatjs.php

cometchatjs.php

1307 ms

f091e643820c909a17b3401ee32a75c2.css

f091e643820c909a17b3401ee32a75c2.css

2147 ms

resolution.css

resolution.css

1084 ms

iphone.css

iphone.css

883 ms

ipad.css

ipad.css

891 ms

d1a8363bf96a2bd71562b7972d2c4f35.js

d1a8363bf96a2bd71562b7972d2c4f35.js

2454 ms

cbd4accffe66540f87817da88b05a05c.js

cbd4accffe66540f87817da88b05a05c.js

2425 ms

mobile_menu.png

mobile_menu.png

213 ms

add.gif

add.gif

405 ms

home-banner.jpg

home-banner.jpg

2513 ms

cometchat_receive.php

cometchat_receive.php

251 ms

icon.png

icon.png

403 ms

icon.png

icon.png

420 ms

icon.png

icon.png

423 ms

hide.png

hide.png

456 ms

cometchat.png

cometchat.png

1075 ms

bgrepeat.png

bgrepeat.png

826 ms

pointer.png

pointer.png

844 ms

tabbottomwhosonline.gif

tabbottomwhosonline.gif

857 ms

action_drop_down.png

action_drop_down.png

900 ms

Accessibility Review

onblr.com accessibility score

63

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

onblr.com best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

onblr.com SEO score

83

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    KR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onblr.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed language. Our system also found out that Onblr.com 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

onblr.com

Open Graph description is not detected on the main page of Onblr. 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: