Website review, no card needed

americor.com logo

americor.com website review

Visit site (opens in a new tab)Reviewed 29 October 202637 issues · 90 checks

This review found 37 issues worth fixing on americor.com, 18 of them high impact, across 90 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 s2.1 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.3 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
136 ms117 msMay 9Oct 24127 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026119 ms
May 16, 2026119 ms
May 23, 2026120 ms
May 30, 2026121 ms
Jun 6, 2026121 ms
Jun 13, 2026123 ms
Jun 20, 2026121 ms
Jun 27, 2026121 ms
Jul 4, 2026122 ms
Jul 11, 2026127 ms
Jul 18, 2026124 ms
Jul 25, 2026130 ms
Aug 1, 2026129 ms
Aug 8, 2026129 ms
Aug 15, 2026131 ms
Aug 22, 2026130 ms
Aug 29, 2026129 ms
Sep 5, 2026124 ms
Sep 12, 2026127 ms
Sep 19, 2026128 ms
Sep 26, 2026130 ms
Oct 3, 2026134 ms
Oct 10, 2026132 ms
Oct 17, 2026129 ms
Oct 24, 2026127 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 americor.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. americor.com at 0.8 s0.8 s
  2. americor.com at 1.7 s1.7 s
  3. americor.com at 2.5 s2.5 s
  4. americor.com at 3.4 s3.4 s
  5. americor.com at 4.2 s4.2 s
  6. americor.com at 5.0 s5.0 s
  7. americor.com at 5.9 s5.9 s
  8. americor.com at 6.7 s6.7 s

Speed

10 to fix36
  • Reduce unused JavaScript

    5.3 s · 1.1 MB

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

  • Render-blocking requests

    2.5 s

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

  • Use efficient cache lifetimes

    1.6 s · 240 KiB

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

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and posthog.com and others), adding 2.3 MB and 2.2 s of main-thread time.

  • Google Tag Manager adds 955 ms

    955 ms

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

  • Reduce unused CSS

    600 ms · 61 KiB

    About 61 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.

  • Google CDN adds 440 ms

    440 ms

    Google CDN costs a phone 440 ms of main-thread work and 742 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.

  • 20 long tasks on the main thread

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

  • Improve image delivery

    150 ms · 53 KiB

    3 images could be 53 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    21 KiB

    Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    12 KiB

    12 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

  • 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: 4 ms

    4 ms

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

Core Web Vitals

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

  • First Contentful Paint: 8.4 s

    8.4 s

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

  • Largest Contentful Paint: 18.8 s

    18.8 s

    Your largest element takes 18.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “One Of The Leading Providers Of Debt Relief Solutions Becom…”.

  • Time to Interactive: 25.6 s

    25.6 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • Total Blocking Time: 881 ms

    881 ms

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 951 ms

    951 ms

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

  • 14 images without width and height

    14 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 127 ms

    127 ms

    Real visitors wait 127 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix45
  • Page weight: 4.2 MB in 175 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 175 requests on a phone: scripts 2.5 MB (44), images 1.1 MB (48) and other files 410 KiB (65). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Founding-Member.png weighs 732 KiB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (732 KiB) is 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.

  • 2 images below the first screen load straight away

    2 images further down the page (60 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.20 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8089
  • Unlabelled dropdowns

    2 dropdowns have no label.

  • 7 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 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 (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 8 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3, h2 → h5 and h2 → h4), 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. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 8598
  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 46 internal links, 17 external

    The homepage links to 46 pages on americor.com and 17 external pages.

8 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Achieve financial freedom with Americor's industry-leading debt relief solutions. Explore our debt consolidation loans,…”.

  • One H1 headline

    Your main headline reads: “One Of The Leading Providers Of Debt Relief Solutions”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Americor: Debt Consolidation and Debt Settlement”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: AboutPage, Organization, Place, 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://americor.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://americor.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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 7 pages without a meta description

    https://americor.com/client-stories, https://americor.com/case-studies, https://americor.com/reviews, https://americor.com/blog, https://americor.com/faqs and https://americor.com/careers and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://americor.com/how-it-works and https://americor.com/about have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=137006815&tm=gtm002&Ver=2&mid=c1659700-9aaa-4902-939f-ef125d8b25f1&bo=1&sid=f9f566a0d3b511f1af7745b928675c6c&vid=f9f577c0d3b511f1a40a350a2c44f06f&vids=1&msclkid=N&pi=9.

  • 5 small tap targets

    5 of 11 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.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID”.

  • 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

1 to fix94
  • 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.

  • About 1,001 words of copy

    The homepage carries about 1,001 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: “Apply Now”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Apply”, “Contact” and “Apply now”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: a star rating and 7 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and PostHog.

  • Direct contact links

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

  • Phone number on the homepage

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies (measured from a US location before any click).

  • 39 other companies contacted

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

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) loads with the page.

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 americor.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
Tailwind CSS
Analytics
Google Tag Manager | PostHog
Hosting
Cloudflare

Company

Employees
1,108
Founded
2008
Headquarters
Irvine

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on americor.com, including 19 speed issues, 1 SEO issue 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