Tools & Wizards About Us
onebonsai.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

onebonsai.com

OneBonsai - Immersive Business Solutions

Page Load Speed

2.9 sec in total

First Response

58 ms

Resources Loaded

1.7 sec

Page Rendered

1.1 sec

onebonsai.com screenshot

About Website

Visit onebonsai.com now to see the best up-to-date One Bonsai content and also check out these interesting facts you probably never knew about onebonsai.com

At OneBonsai we create professional Augmented and Virtual Experiences to help get your company metaverse ready!

Visit onebonsai.com

Key Findings

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

Performance Metrics

onebonsai.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value16.0 s

0/100

10%

TBT (Total Blocking Time)

Value18,680 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value42.1 s

0/100

10%

Network Requests Diagram

onebonsai.com

58 ms

onebonsai.com

953 ms

gtm.js

63 ms

uc.js

53 ms

basic.min.css

28 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 84% of them (71 requests) were addressed to the original Onebonsai.com, 4% (3 requests) were made to Use.fontawesome.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (953 ms) belongs to the original domain Onebonsai.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 811.5 kB (48%)

Content Size

1.7 MB

After Optimization

892.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Onebonsai.com main page is 1.7 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. 75% 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. HTML takes 796.6 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 714.6 kB

  • Original 796.6 kB
  • After minification 795.6 kB
  • After compression 82.0 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 714.6 kB or 90% of the original size.

JavaScript Optimization

-12%

Potential reduce by 96.6 kB

  • Original 775.2 kB
  • After minification 775.2 kB
  • After compression 678.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 96.6 kB or 12% of the original size.

CSS Optimization

-0%

Potential reduce by 203 B

  • Original 131.6 kB
  • After minification 131.6 kB
  • After compression 131.4 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. Onebonsai.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 74 (97%)

Requests Now

76

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

onebonsai.com

onebonsai.com

58 ms

onebonsai.com

onebonsai.com

953 ms

gtm.js

gtm.js

63 ms

uc.js

uc.js

53 ms

basic.min.css

basic.min.css

28 ms

theme-ie11.min.css

theme-ie11.min.css

31 ms

theme.min.css

theme.min.css

52 ms

intlTelInput.min.css

intlTelInput.min.css

31 ms

style.css

style.css

39 ms

formreset.min.css

formreset.min.css

49 ms

formsmain.min.css

formsmain.min.css

40 ms

readyclass.min.css

readyclass.min.css

46 ms

browsers.min.css

browsers.min.css

50 ms

front.min.css

front.min.css

52 ms

style.min.css

style.min.css

54 ms

style.min.css

style.min.css

53 ms

style.min.css

style.min.css

79 ms

theme.min.css

theme.min.css

77 ms

header-footer.min.css

header-footer.min.css

80 ms

elementor-icons.min.css

elementor-icons.min.css

81 ms

frontend.min.css

frontend.min.css

83 ms

swiper.min.css

swiper.min.css

19 ms

frontend.min.css

frontend.min.css

27 ms

all.css

all.css

19 ms

general.min.css

general.min.css

13 ms

css

css

44 ms

jquery.min.js

jquery.min.js

20 ms

jquery-migrate.min.js

jquery-migrate.min.js

26 ms

jquery.json.min.js

jquery.json.min.js

39 ms

gravityforms.min.js

gravityforms.min.js

39 ms

utils.min.js

utils.min.js

39 ms

conditional_logic.min.js

conditional_logic.min.js

40 ms

app.js

app.js

306 ms

6929251.js

6929251.js

307 ms

widget.js

widget.js

268 ms

email-decode.min.js

email-decode.min.js

266 ms

hotjar-712160.js

hotjar-712160.js

404 ms

spai-lib-bg-compat.1.1.min.js

spai-lib-bg-compat.1.1.min.js

388 ms

Nexa-Regular.woff

Nexa-Regular.woff

240 ms

Nexa-Book.woff

Nexa-Book.woff

237 ms

Nexa-Bold.woff

Nexa-Bold.woff

238 ms

Nexa-Heavy.woff

Nexa-Heavy.woff

239 ms

animations.min.css

animations.min.css

68 ms

general.min.js

general.min.js

69 ms

eael-1690.js

eael-1690.js

136 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

137 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

136 ms

wp-polyfill.min.js

wp-polyfill.min.js

135 ms

dom-ready.min.js

dom-ready.min.js

135 ms

hooks.min.js

hooks.min.js

135 ms

i18n.min.js

i18n.min.js

214 ms

a11y.min.js

a11y.min.js

213 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

214 ms

vendor-theme.min.js

vendor-theme.min.js

214 ms

scripts-theme.min.js

scripts-theme.min.js

213 ms

intlTelInput-jquery.min.js

intlTelInput-jquery.min.js

212 ms

utils.js

utils.js

431 ms

init.js

init.js

450 ms

api.js

api.js

229 ms

frontend.min.js

frontend.min.js

430 ms

jquery.textareaCounter.plugin.min.js

jquery.textareaCounter.plugin.min.js

449 ms

front.min.js

front.min.js

448 ms

hello-frontend.min.js

hello-frontend.min.js

509 ms

googlesitekit-consent-mode-3d6495dceaebc28bcca3.js

googlesitekit-consent-mode-3d6495dceaebc28bcca3.js

509 ms

eael-12524.js

eael-12524.js

513 ms

jquery.sticky.min.js

jquery.sticky.min.js

513 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

508 ms

imagesloaded.min.js

imagesloaded.min.js

508 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

518 ms

webpack.runtime.min.js

webpack.runtime.min.js

519 ms

frontend-modules.min.js

frontend-modules.min.js

521 ms

frontend.min.js

frontend.min.js

517 ms

waypoints.min.js

waypoints.min.js

519 ms

core.min.js

core.min.js

517 ms

fa-solid-900.woff

fa-solid-900.woff

352 ms

fa-regular-400.woff

fa-regular-400.woff

405 ms

fa-brands-400.woff

fa-brands-400.woff

493 ms

banner.js

banner.js

426 ms

collectedforms.js

collectedforms.js

404 ms

fb.js

fb.js

403 ms

6929251.js

6929251.js

403 ms

frontend.min.js

frontend.min.js

462 ms

elements-handlers.min.js

elements-handlers.min.js

461 ms

lazyload.min.js

lazyload.min.js

460 ms

recaptcha__en.js

recaptcha__en.js

289 ms

Accessibility Review

onebonsai.com accessibility score

65

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-*] attributes do not match their roles

High

[role]s do not have all required [aria-*] attributes

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

onebonsai.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

onebonsai.com SEO score

86

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

onebonsai.com

Open Graph data is detected on the main page of One Bonsai. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: