sanriaengineering.com website review

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

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

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

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

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

About 132 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

Unpkg costs a phone 352 ms of main-thread work and 96 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 third-party services load with your homepage (Unpkg, turbify.com and JSDelivr CDN and others), adding 351 KiB and 468 ms of main-thread time.

12 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Connection Design Engineering”.

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

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

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

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

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.

Your homepage downloads 18.8 MB in 84 requests on a phone: media 10.3 MB (1), images 6.7 MB (29) and other files 1.1 MB (3). Under 2 MB keeps phones on slow connections fast.

intersection.jpg weighs 604 KiB. On a phone connection a single image that size takes seconds.

6 images (1.5 MB) 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 (730 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

6 images are downloaded at several times the size a phone draws them, for example intersection.jpg at 1,135 px wide, shown at 358 px. Resized copies would save about 110 KiB.

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

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

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

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

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

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

The page declares lang=“zxx”, which is not a usable language code (“zxx” means “no linguistic content”), so screen readers and translation tools guess.

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

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

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

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

There are 5 <h1> headlines (“Revolutionizing Engineering”, “Savannah Convention Center” and “Wilson School”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

The homepage links to 29 pages on sanriaengineering.com and 2 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://sanriaengineering.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://sanriaengineering.com/about.html, https://sanriaengineering.com/our-expertise.html, https://sanriaengineering.com/projects.html, https://sanriaengineering.com/quality-standards.html, https://sanriaengineering.com/contact-us.html and https://sanriaengineering.com/projects/convention-center/savannah-convention-center.html and 8 others use the same meta description. A description written for each page earns more clicks.

https://sanriaengineering.com/about.html, https://sanriaengineering.com/our-expertise.html, https://sanriaengineering.com/projects.html, https://sanriaengineering.com/quality-standards.html, https://sanriaengineering.com/contact-us.html and https://sanriaengineering.com/case-studies.html and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://sanriaengineering.com/projects.html, https://sanriaengineering.com/projects/airport-support-facility/united-airlines.html and https://sanriaengineering.com/software.html have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 14 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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