Website review, no card needed
vbeyond.com website review
Visit site (opens in a new tab)Reviewed 20 November 202624 issues · 72 checks
This review found 24 issues worth fixing on vbeyond.com, 14 of them high impact, across 72 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 5.5 s |
| Jun 6, 2026 | 4.3 s |
| Jun 13, 2026 | 4.4 s |
| Jun 20, 2026 | 4.7 s |
| Jun 27, 2026 | 4.5 s |
| Jul 4, 2026 | 4.4 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.6 s |
| Aug 1, 2026 | 4.7 s |
| Aug 8, 2026 | 4.8 s |
| Aug 15, 2026 | 4.9 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 5.2 s |
| Sep 5, 2026 | 5.4 s |
| Sep 12, 2026 | 5.7 s |
| Sep 19, 2026 | 6.1 s |
| Sep 26, 2026 | 6.1 s |
| Oct 3, 2026 | 6.1 s |
| Oct 10, 2026 | 6.3 s |
| Oct 17, 2026 | 6.2 s |
| Oct 24, 2026 | 6.2 s |
| Oct 31, 2026 | 6.0 s |
| Nov 7, 2026 | 5.8 s |
| Nov 14, 2026 | 5.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 126 ms |
| Jun 6, 2026 | 141 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 135 ms |
| Jun 27, 2026 | 135 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 139 ms |
| Jul 18, 2026 | 149 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 116 ms |
| Aug 15, 2026 | 98 ms |
| Aug 22, 2026 | 97 ms |
| Aug 29, 2026 | 97 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 111 ms |
| Sep 19, 2026 | 114 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 118 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 130 ms |
| Oct 31, 2026 | 116 ms |
| Nov 7, 2026 | 106 ms |
| Nov 14, 2026 | 99 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
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 5.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.2 s
5.2 sReal visitors see the first content after 5.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 5.5 s to 5.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 95 ms
95 msReal visitors wait 95 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Tap response (INP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 126 ms to 99 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
About 0.5 g of CO₂ per visit
0.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.50 g of CO₂e: 60.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.8 MB
1.8 MBYour homepage downloads 1.8 MB on a phone, 268 KiB of it images (15%). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
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.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Hidden but focusable
9 elements hidden from screen readers can still receive keyboard focus.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA commands must have an accessible name (2 elements)
ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (26 elements)
All page content should be contained by landmarks: 26 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 70 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 64 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 15 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
166 internal links, 5 external
The homepage links to 166 pages on vbeyond.com and 5 external pages.
8 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “VBeyond delivers recruitment and staffing solutions for permanent hiring, contract staffing, tech talent, and RPO sacro…”.
One H1 headline
Your main headline reads: “Where Talent Meets Opportunity”.
Title: 51 characters
Your title is a healthy 51 characters: “Global Recruitment and Staffing Solutions | VBeyond”.
Canonical URL set
The canonical URL is https://www.vbeyond.com/.
Structured data in place
Structured data found: 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://www.vbeyond.com/sitemap_index.xml.
AI search readiness
4 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,358 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.vbeyond.com/llms.txt (39 KiB, 87 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
10 pages slow to respond
https://www.vbeyond.com/services/contract-staffing, https://www.vbeyond.com/services/tech-staffing, https://www.vbeyond.com/services/permanent-hiring, https://www.vbeyond.com/services/recruitment-process-outsourcing, https://www.vbeyond.com/industry/it-technology-staffing-solutions and https://www.vbeyond.com/industry/bfsi-staffing-solutions and 4 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 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 a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 small tap targets
10 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 1,423 words of copy
The homepage carries about 1,423 words of visible text.
6 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact Us” and “DOWNLOAD NOW”.
1 short form
A short form (6 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 17 testimonial or review blocks, 3 trust badges and “150 + Clients”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
9 other companies contacted
Loading the homepage contacts 9 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 vbeyond.com, 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
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on vbeyond.com, including 4 speed issues and 2 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.