Website review, no card needed

ofgltd.com logo

ofgltd.com website review

Visit site (opens in a new tab)Reviewed 28 October 202633 issues · 84 checks

This review found 33 issues worth fixing on ofgltd.com, 13 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.4 s1.1 sMay 9Oct 241.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.5 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.5 s
Jul 4, 20261.4 s
Jul 11, 20261.3 s
Jul 18, 20261.5 s
Jul 25, 20261.7 s
Aug 1, 20262.0 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20262.1 s
Sep 12, 20262.2 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.5 s
Oct 24, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
95 ms77 msSep 19Oct 1793 ms
Show as table
DateReal-visitor tap response (INP)
Sep 19, 202679 ms
Sep 26, 202680 ms
Oct 3, 202680 ms
Oct 10, 202680 ms
Oct 17, 202693 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

Full-page screenshot of ofgltd.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ofgltd.com at 0.6 s0.6 s
  2. ofgltd.com at 1.2 s1.2 s
  3. ofgltd.com at 1.8 s1.8 s
  4. ofgltd.com at 2.3 s2.3 s
  5. ofgltd.com at 2.9 s2.9 s
  6. ofgltd.com at 3.5 s3.5 s
  7. ofgltd.com at 4.1 s4.1 s
  8. ofgltd.com at 4.7 s4.7 s

Speed

12 to fix44
  • Reduce unused JavaScript

    15.6 s · 2.8 MB

    About 2.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 15.6 s faster on a phone.

  • Improve image delivery

    12.8 s · 2.6 MB

    4 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.8 s faster on a phone.

  • Render-blocking requests

    2.9 s

    47 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44 (desktop: 57). 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, Macropod BugHerd and Accessibe Accessibility Overlay and others), adding 3.5 MB and 789 ms of main-thread time.

  • Reduce unused CSS

    600 ms · 110 KiB

    About 110 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Macropod BugHerd adds 282 ms

    282 ms

    Macropod BugHerd costs a phone 282 ms of main-thread work and 2.6 MB 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.

  • Google Tag Manager adds 394 ms

    394 ms

    Google Tag Manager costs a phone 394 ms of main-thread work and 606 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.

  • Use efficient cache lifetimes

    350 ms · 60 KiB

    7 files are served with short cache lifetimes, so returning visitors download them again (60 KiB).

  • Legacy JavaScript

    350 ms · 8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

  • Main-thread work: 2.5 s

    A phone's processor spends 2.5 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 2,072 HTML elements

    The page has 2,072 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 229 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify CSS

    14 KiB

    14 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 23 ms

    23 ms

    Your server sent the HTML in 23 ms, well inside Google's 600 ms guideline.

Core Web Vitals

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

  • Largest Contentful Paint: 44.4 s

    44.4 s

    Your largest element takes 44.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THOUGHTFUL. INSIGHTFUL. COMMITTED.® Speak with a Managing D…”.

  • Speed Index: 17.8 s

    17.8 s

    Visually, the page fills in at 17.8 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 44.4 s

    44.4 s

    The page becomes fully interactive after 44.4 s. Good is under 3.8 s.

  • First Contentful Paint: 5.3 s

    5.3 s

    The first text or image appears after 5.3 s on a phone. Good is under 1.8 s.

  • Real-user TTFB: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 468 ms

    468 ms

    Scripts block taps and scrolling for 468 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    +9%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 79 ms to 93 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 7.8 MB in 137 requests

    7.8 MB

    Your homepage downloads 7.8 MB in 137 requests on a phone: scripts 3.7 MB (59), images 3.5 MB (13) and fonts 285 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (309 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 2.2 g of CO₂ per visit

    2.21 g

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

2 checks passed
  • 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

6 to fixGoogle 8592
  • 19 text elements with low contrast

    19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (44 elements)

    All page content should be contained by landmarks: 44 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 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9284
  • Title is long (87 characters)

    Your title is 87 characters, so Google will cut it off around 60: “Wealth Management & Registered Investment Advisor (RIA) | Oxford Financial Group, Ltd.™”.

  • Meta description is long (182 characters)

    Your meta description is 182 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 4 problems

    Structured data found (LocalBusiness, Organization, Service and SiteNavigationElement) but with 4 problems, for example “Organization: sameAs is an empty list”.

  • 592 internal links, 20 external

    The homepage links to 592 pages on ofgltd.com and 20 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Thoughtful. Insightful. Committed.®”.

  • Canonical URL set

    The canonical URL is https://ofgltd.com/.

  • 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://ofgltd.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://ofgltd.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.

3 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, sameAs (social profiles), description and contact details; logo would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,465 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without a meta description

    https://ofgltd.com/about-us/privacy-and-security has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 133 found) and read each the way a search engine does.

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

  • 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

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'slideTo')”.

2 checks passed
  • Tap targets are thumb-sized

    17 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix89
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 600 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more about us”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us” and “Learn more about us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 18 other companies contacted

    Loading the homepage contacts 18 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 ofgltd.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 Analytics | Google Tag Manager
Hosting
Google Cloud

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on ofgltd.com, including 19 speed issues, 3 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25