proresource.com website review

About 484 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

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

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

8 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

7 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and flodesk.com and others), adding 1.1 MB and 550 ms of main-thread time.

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

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

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

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

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

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

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 8.1 s on a phone. Good is under 1.8 s.

Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LinkedIn for CEOs Powerful, authentic personal branding for…”.

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

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

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

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.

Your homepage downloads 3.4 MB in 80 requests on a phone: images 1.5 MB (14), scripts 1.1 MB (30) and other files 367 KiB (10). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example ProResource-How-to-Craft-a-CEO-Brand-2026-Edition.webp at 1,368 px wide, shown at 204 px. Resized copies would save about 71 KiB.

1 image (182 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 further down the page (110 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 36 pages on proresource.com and 23 external pages.

/services/ceo-linkedin-profile-writing and /ceo-linkedin-profile-writing all use the title “CEO LinkedIn Profile Writing - ProResource”. Search engines can't tell which page to show for a search, so each competes with the others.

/services/ceo-linkedin-profile-writing and /ceo-linkedin-profile-writing use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /ceo-linkedin-profile-writing, whose canonical is /services/ceo-linkedin-profile-writing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/excellent-examples-of-executives-on-linkedin and /blog have no <h1> headline, so visitors and search engines get no clear main topic.

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

8 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://assets.flodesk.com/flodesk-sans.css' from origin 'https://www.proresource.com' has…”.

1 image is served at too low a resolution for sharp phone screens.

1 link from your homepage to your own site is broken, for example https://www.proresource.com/cdn-cgi/l/email-protection (404).

8 links to other sites are dead, for example https://www.linkedin.com/in/lewis-johnson-468679/ (999).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

proresource.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

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

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

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.

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

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

DMARC is set to p=none, so mail pretending to be proresource.com is still delivered. Add a report address, check the reports, then move to quarantine.

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.

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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.