pwcpa.com website review

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

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

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

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

7 third-party services load with your homepage (Squarespace, Google Tag Manager and Google CDN and others), adding 4.3 MB and 965 ms of main-thread time.

Squarespace costs a phone 735 ms of main-thread work and 961 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.

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

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 2.5 MB 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.

Adobe TypeKit costs a phone 10 ms of main-thread work and 570 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 244 ms. During a long task the page ignores taps.

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

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

Desktop scores 73 but mobile only 45. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

Your largest element takes 20.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “We’re in the Knowledge Business”.

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

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

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

1 image 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 4.4 MB in 106 requests on a phone: images 2.5 MB (12), scripts 1.1 MB (57) and fonts 584 KiB (21). Under 2 MB keeps phones on slow connections fast.

2 images further down the page (369 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 1.23 g of CO₂e: 148.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Your title is only 15 characters: “Perelson Weiner”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/6a582d59d38bf5224ea…”.

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

The homepage links to 49 pages on pwcpa.com and 0 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.

There is no /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.

/about-us and /about-us-1 all use the title “About Us — Perelson Weiner”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/about-us, /awards, /private-company-corporate-services, /non-profit-foundation-services, /services-overview and /insights and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

/tax-strategy, /high-net-worth-services and /nycaccountingandauditclienttypesanservices use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /about-us-1, whose canonical is /about-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/about-us, /careers, /private-company-corporate-services, /non-profit-foundation-services, /ourprofessionals and /about-us-1 have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.pwcpa.com/s/plugin-lightbox.css' because its MIME type ('text/html') is not a …”.

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

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

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.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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