Website review, no card needed
valbury.co.id website review
Visit site (opens in a new tab)Reviewed 31 October 202649 issues · 88 checks
This review found 49 issues worth fixing on valbury.co.id, 22 of them high impact, across 88 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.0 s |
| May 16, 2026 | 4.2 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 4.6 s |
| Aug 1, 2026 | 6.2 s |
| Aug 8, 2026 | 6.6 s |
| Aug 15, 2026 | 6.6 s |
| Aug 22, 2026 | 6.8 s |
| Aug 29, 2026 | 6.6 s |
| Sep 5, 2026 | 6.5 s |
| Sep 12, 2026 | 6.9 s |
| Sep 19, 2026 | 6.8 s |
| Sep 26, 2026 | 6.7 s |
| Oct 3, 2026 | 6.5 s |
| Oct 10, 2026 | 4.5 s |
| Oct 17, 2026 | 3.7 s |
| Oct 24, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 292 ms |
| May 16, 2026 | 316 ms |
| May 23, 2026 | 335 ms |
| May 30, 2026 | 348 ms |
| Jun 6, 2026 | 352 ms |
| Jun 13, 2026 | 343 ms |
| Jun 20, 2026 | 330 ms |
| Jun 27, 2026 | 323 ms |
| Jul 4, 2026 | 323 ms |
| Jul 11, 2026 | 315 ms |
| Jul 18, 2026 | 316 ms |
| Jul 25, 2026 | 347 ms |
| Aug 1, 2026 | 389 ms |
| Aug 8, 2026 | 400 ms |
| Aug 15, 2026 | 408 ms |
| Aug 22, 2026 | 410 ms |
| Aug 29, 2026 | 414 ms |
| Sep 5, 2026 | 422 ms |
| Sep 12, 2026 | 440 ms |
| Sep 19, 2026 | 442 ms |
| Sep 26, 2026 | 444 ms |
| Oct 3, 2026 | 442 ms |
| Oct 10, 2026 | 407 ms |
| Oct 17, 2026 | 401 ms |
| Oct 24, 2026 | 396 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Render-blocking requests
5.1 s44 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.1 s.
Use efficient cache lifetimes
3.3 s · 1.6 MB107 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
Reduce unused JavaScript
2.7 s · 801 KiBAbout 801 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Improve image delivery
1.1 s · 562 KiB12 images could be 562 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Freshchat and Facebook and others), adding 2.2 MB and 1.4 s of main-thread time.
Google Tag Manager adds 668 ms
668 msGoogle Tag Manager costs a phone 668 ms of main-thread work and 681 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Freshchat adds 370 ms
370 msFreshchat costs a phone 370 ms of main-thread work and 840 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 338 ms. During a long task the page ignores taps.
2,137 HTML elements
The page has 2,137 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Facebook adds 174 ms
174 msFacebook costs a phone 174 ms of main-thread work and 297 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Legacy JavaScript
150 ms · 41 KiBPolyfills for old browsers add 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 40 KiBAbout 40 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 559 ms
559 msYour server sent the HTML in 559 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 5.4 s
5.4 sReal visitors wait 5.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.0 s
5.0 sReal visitors see the first content after 5.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.8 s
2.8 sReal visitors wait 2.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 15.5 s
15.5 sYour largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Investasi Aset Global Jadi Lebih Aman, Mudah dan Maksimal T…”.
Speed Index: 14.8 s
14.8 sVisually, the page fills in at 14.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 21.6 s
21.6 sThe page becomes fully interactive after 21.6 s. Good is under 3.8 s.
First Contentful Paint: 5.7 s
5.7 sThe first text or image appears after 5.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 686 ms
686 msScripts block taps and scrolling for 686 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 345 ms
345 msReal visitors wait 345 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 292 ms to 396 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.6 MB in 194 requests
3.6 MBYour homepage downloads 3.6 MB in 194 requests on a phone: scripts 2.4 MB (67), images 900 KiB (37) and stylesheets 181 KiB (45). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
1.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.03 g of CO₂e: 123.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Elements must only use permitted ARIA attributes (16 elements)
Elements must only use permitted ARIA attributes: 16 elements on the page fail this check, rated serious by axe-core.
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (33 elements)
All page content should be contained by landmarks: 33 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 11 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Melangkah Bersama Broker yang #LebihBerpengalaman”, “Kebijakan Privasi” and “Syarat & Ketentuan”). One clear main headline is easier for people and search engines.
53 internal links, 13 external
The homepage links to 53 pages on valbury.co.id and 13 external pages.
7 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Broker forex terpercaya di Indonesia, Valbury Asia Futures hadir dengan trading mudah, signal aplikasi, tools, dan laya…”.
Title: 56 characters
Your title is a healthy 56 characters: “Broker Forex Terpercaya Indonesia | Valbury Asia Futures”.
Canonical URL set
The canonical URL is https://valbury.co.id/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://valbury.co.id/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://valbury.co.id/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (4,807 words), so crawlers that don't run JavaScript still read it.
Other pages
4 linked pages hidden from search
https://valbury.co.id/products/futures, https://valbury.co.id/products/saham-as, https://valbury.co.id/events and https://valbury.co.id/calc-redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
/ and https://valbury.co.id/en all use the title “Broker Forex Terpercaya Indonesia | Valbury Asia Futures”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://valbury.co.id/products/futures, https://valbury.co.id/products/saham-as, https://valbury.co.id/products/trading-platform, https://valbury.co.id/journal and https://valbury.co.id/calc-redirect have no meta description, so Google writes the search snippet from whatever text it finds.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343242836&tm=gtm002&Ver=2&mid=86d5d903-e331-4a89-b6a1-d10a21ec0319&bo=1&sid=c3c74d20d51411f1ad2749563fbb641c&vid=c3c774b0d51411f1bd45054df1085d2a&vids=1&msclkid=N&pi=9.
6 small tap targets
6 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://valbury.co.id/wp-content/uploads/elementor/css/loop-323427.css?ver=1784308878' bec…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: “30,000+ Users”. Pairing it with named testimonials or customer logos makes it far more convincing.
A 10-field form
Your longest form asks for 10 fields (10 required). Every extra field lowers completion.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 905 words of copy
The homepage carries about 905 words of visible text.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Request Demo”, “Smart Order” and “Download Sekarang”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
21 cookies set on arrival
21Opening the homepage sets 21 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
26 other companies contacted
Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at valbury.co.id, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on valbury.co.id, including 24 speed issues, 1 SEO issue and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.