myfinancialresources.org — Website Report

Scored 63/100 · Scanned with Foglift

OverallⓘOverall Score — weighted average of all category scores

myfinancialresources.org scored 63. Addressing the 19 listed issues could raise its estimated score to 85.

Scan another domain Save this scan to your free account

3 critical12 warnings19 total issues

Quick wins

~175 min total fix time

1Missing Permissions Policy header~2m

2No main landmark~3m

3Missing Content Security Policy header~5m

https://myfinancialresources.org/ · 2026-08-14

Scanned with Foglift · Technical Audit + AI Readiness analysis

Share This Report

Send this scan to a teammate or contact. The shareable link includes all scores and issues.

Email to Contact

AI Readiness

Technical and authority signals that support AI systems in accessing, understanding, and reusing your content

70C

Some external data sources were unavailable. Score is based on partial data.

Technical68

Authority72

Set up all 6 tiers free →

Brand Mentions

Found 18+ web mentions of "myfinancialresources"

Domain Authority

PageRank: 2.6/10, 20+ external references

—

Content Freshness

Unavailable

Technical Readiness

Moderate technical readiness — some improvements possible

Technical Issues

No FAQ section foundwarning~15 min fix

A clear Frequently Asked Questions section presents important questions and answers in a directly extractable format. Add one when it reflects real customer questions, and keep each answer factual and self-contained.

Quick Fix

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What does your company do?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "We provide [your service]. Our solution helps..."
    }
  }]
}
</script>

FAQPage schema labels questions and answers in a machine-readable format, making the page easier for search and AI systems to extract accurately.

How does AI see Myfinancialresources?

When users ask AI about your industry, are you recommended?

Start with weekly Google AI Overview checks for Myfinancialresources. Paid plans add ChatGPT, Perplexity, Gemini, and Claude.

Set up weekly monitoring free

SEO & Technical Issues (18)

Missing Content Security Policy headercriticalSecurity~5 min fix

Add a Content-Security-Policy header to prevent XSS and injection attacks.

Quick Fix

# Nginx:
add_header Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';" always;

# Apache (.htaccess):
Header set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';"

# Next.js (next.config.js headers):
{ key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' 'unsafe-inline'" }

Content-Security-Policy prevents XSS attacks by controlling which resources the browser can load.

6 images missing alt textcriticalSEO

Found 6 of 27 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).

19 render-blocking scriptscriticalPerformance

19 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.

Missing Permissions Policy headerwarningSecurity~2 min fix

Add a Permissions-Policy header to control browser feature access.

Quick Fix

# Nginx:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;

# Next.js (next.config.js headers):
{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=()' }

Permissions-Policy restricts which browser features your site can use, reducing attack surface.

Title tag too longwarningSEO

Your title is 73 characters. Keep it under 60 for best display in search results.

Multiple H1 headings foundwarningSEO

Found 2 H1 headings. Best practice is to have exactly one H1 per page for clear content hierarchy.

No sitemap.xml foundwarningSEO~15 min fix

Your site is missing a sitemap.xml file. Sitemaps help search engines discover and index all your pages. Submit one to Google Search Console.

Quick Fix

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://yoursite.com/</loc>
    <lastmod>2026-03-15</lastmod>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://yoursite.com/about</loc>
    <lastmod>2026-03-15</lastmod>
    <priority>0.8</priority>
  </url>
</urlset>

A sitemap.xml helps search engines discover and index all your pages. Place it at your site root.

22% of images lack alt textwarningAccessibility

6 of 27 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.

Skipped heading levelwarningAccessibility

Heading hierarchy jumps from H1 to H3. Don't skip heading levels — this confuses screen readers and assistive technology.

Potential low contrast textwarningAccessibility

Some text appears to use light colors that may not have sufficient contrast against the background. WCAG requires a minimum 4.5:1 contrast ratio.

Large HTML documentwarningPerformance

Your HTML is 248KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.

10 third-party scripts loadedwarningPerformance

Your page loads 10 scripts from external domains. Consider auditing trackers and widgets and deferring non-critical ones.

23 external stylesheetswarningPerformance

Loading 23 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.

11 images without lazy loadingwarningPerformance

11 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.

Few internal linksinfoSEO

Add more internal links to help search engines discover and index your other pages. Internal linking also helps distribute page authority.

No main landmarkinfoAccessibility~3 min fix

Add a <main> element to identify the primary content area. Screen reader users use this to skip navigation.

Quick Fix

<!-- Wrap your primary content in a <main> element -->
<main id="main-content">
  <h1>Page Title</h1>
  <p>Your primary content here...</p>
</main>

The <main> element identifies the primary content area, letting screen reader users skip to it directly.

No skip navigation linkinfoAccessibility~5 min fix

Add a 'Skip to main content' link at the top of the page so keyboard users can bypass repetitive navigation.

Quick Fix

<!-- Add as the first element inside <body> -->
<a href="#main-content" class="sr-only focus:not-sr-only focus:absolute focus:top-2 focus:left-2 focus:z-50 focus:px-4 focus:py-2 focus:bg-blue-600 focus:text-white focus:rounded">
  Skip to main content
</a>

<!-- Add id to your main content area -->
<main id="main-content">
  ...
</main>

Skip links let keyboard users bypass repetitive navigation and jump straight to content.

HTML contains many commentsinfoPerformance

Found 26 HTML comments. Remove unnecessary comments in production to reduce file size.

Your Potential Score

Now

Estimated potential

+22 points estimated improvement from addressing 19 listed issues

Estimate based on the measured category scores and the issues listed in this audit.

Track your AI visibility over time

AI Visibility Monitoring

Free checks Google AI Overview weekly while you're active. Paid plans add ChatGPT, Perplexity, Gemini, and Claude with daily, twice-daily, or hourly monitoring.

Competitor Tracking

Compare your AI visibility against competitors. Know when they overtake you.

Weekly Digest

Get AI-generated insights emailed every Monday with action items.

Set up Free monitoring

Weekly Google AI Overview while active · No credit card required

Compare paid plans — from $49/mo