pcsrcs.com website review

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

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

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

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

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

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

4 third-party services load with your homepage (Google Maps, Cloudflare and intelligentcloudforesight.com and others), adding 361 KiB and 71 ms of main-thread time.

1 long task block the main thread while loading, the longest for 60 ms. During a long task the page ignores taps.

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

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

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

9 KiB could be saved by minifying CSS.

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.

3 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (5.5 s).

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

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

1 image (51 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.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is 68 characters, so Google will cut it off around 60: “School Lunch POS | K-12 School Nutrition Software – School Lunch POS”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“Solutions”, “Testimonials” and “About PCS”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://pcsrcs.com/sitemap.xml, so Google discovers your pages only by following links.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 45 pages on pcsrcs.com and 6 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 https://pcsrcs.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.

https://pcsrcs.com/about-us, https://pcsrcs.com/pcs-solutions, https://pcsrcs.com/pcs-solutions/fr-accountability-pos, https://pcsrcs.com/pcs-solutions/fr-accountability-pos/webpos, https://pcsrcs.com/pcs-solutions/fr-accountability-pos/applynow and https://pcsrcs.com/pcs-solutions/parent-account-portal/320-alternative-application and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://pcsrcs.com/pcs-solutions/fr-accountability-pos/webpos, https://pcsrcs.com/pcs-solutions/pcsforms/508-account-collection-management and https://pcsrcs.com/pcs-solutions/pcsforms/502-special-diets have no <h1> headline, so visitors and search engines get no clear main topic.

https://pcsrcs.com/about-us, https://pcsrcs.com/pcs-solutions, https://pcsrcs.com/pcs-solutions/fr-accountability-pos, https://pcsrcs.com/pcs-solutions/fr-accountability-pos/webpos, https://pcsrcs.com/pcs-solutions/fr-accountability-pos/applynow and https://pcsrcs.com/pcs-solutions/parent-account-portal/320-alternative-application and 9 others took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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

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