c2cresources.com website review

Your mobile performance score is 71 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

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

About 362 KiB of JavaScript is downloaded but never used on this page.

4 third-party services load with your homepage (Google Tag Manager, Vimeo and Google Fonts and others), adding 1.0 MB and 181 ms of main-thread time.

Vimeo costs a phone 33 ms of main-thread work and 510 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.

Google Fonts costs a phone 0 ms of main-thread work and 367 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.

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

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

About 22 KiB of CSS is downloaded but never applied on this page.

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

5 KiB could be saved by minifying CSS.

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

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

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Commercial Collection Agency for Past Due B2B Accounts”.

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

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

The layout shifts by 0.109 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4 images (514 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.

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

1 image is downloaded at several times the size a phone draws it, for example infomax-collection-graphic-2.png at 1,000 px wide, shown at 314 px. Resized copies would save about 38 KiB.

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

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

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

The homepage links to 33 pages on c2cresources.com and 4 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

Chrome logged issues while loading the page (“Cookie”).

2 links to other sites are dead, for example https://app.c2cresources.com/pmax/display.asp?formatoption=signin (404).

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

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 533 words of visible text.

DMARC is set to p=none, so mail pretending to be c2cresources.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 and 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.

Opening the homepage sets 4 cookies, 2 of them by other companies (measured from a US location before any click).

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.

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