foundationsoft.com website review

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

Google CDN costs a phone 1.3 s of main-thread work and 2.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 3.4 MB and 2.7 s of main-thread time.

Google Tag Manager costs a phone 740 ms of main-thread work and 813 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 files are served with short cache lifetimes, so returning visitors download them again (302 KiB).

20 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

Facebook costs a phone 285 ms of main-thread work and 212 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 block the main thread while loading, the longest for 280 ms. During a long task the page ignores taps.

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

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

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

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

2 images could be 11 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Your largest element takes 24.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “banner”.

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

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

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

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

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

Your homepage downloads 6.7 MB in 203 requests on a phone: scripts 3.8 MB (78), fonts 1.3 MB (17) and other files 751 KiB (41). Under 2 MB keeps phones on slow connections fast.

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

16 elements hidden from screen readers can still receive keyboard focus.

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

1 image has no alt text, which hurts accessibility and image search.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

Your title is 76 characters, so Google will cut it off around 60: “Construction Accounting Software Built for Contractors | Foundation Software”.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 167 pages on foundationsoft.com and 43 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5740310&tm=gtm002&Ver=2&mid=8a4cb75d-3225-4541-8cb9-0a495aaa0c42&bo=2&sid=8fff9760d4d311f1a4c0b53dd23b8dfc&vid=8fffbab0d4d311f19b282be728f146d4&vids=1&msclkid=N&pi=918.

2 errors were logged to the browser console while the page loaded, for example “Cannot set properties of null (setting 'value')”.

1 link go through two or more redirects, for example https://cvent.me/yBDP12?rt=mG540RtSoEmJC2_06F9qYw&RefId=ClientRegFSLSite.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

foundationsoft.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

foundationsoft.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 826 words of visible text.

DMARC is set to p=none, so mail pretending to be foundationsoft.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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