orabasesolutions.com website review

• Google's speed test didn't respond

  Google's speed test didn't respond for this site, so speed and Core Web Vitals are not measured here. Your full playbook measures them.

Not measured in this review.

• About 0.3 g of CO₂ per visit

  0.28 g

  By the Sustainable Web Design model, a visit to your homepage emits about 0.28 g of CO₂e: 33.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• Zoom is disabled

  The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  Elements (1)

• Page should contain a level-one heading (1 element)

  Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Headings skip levels

  Headings skip levels (h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.

  View source

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• No social preview image

  No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  View source

• 43 internal links, 3 external

  The homepage links to 43 pages on orabasesolutions.com and 3 external pages.

• No llms.txt

  There is no https://www.orabasesolutions.com/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 pages slow to respond

  https://www.orabasesolutions.com/career/senior-ui-developer and https://www.orabasesolutions.com/career/oracle-database-administrator-2 took over 3 s to send their HTML from our server.

• 13 internal pages checked

  We fetched 13 pages linked from your homepage and read each the way a search engine does.

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

• 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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

• Phone number is not tap-to-call

  Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

• 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 627 words of copy

  The homepage carries about 627 words of visible text.

• 1 tracker load before any consent

  1

  Before a visitor clicks anything, the page loads Google Tag Manager (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.

• 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.

• 3 other companies contacted

  Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.