pillar.tech website review

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

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

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

8 images could be 1,019 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

5 third-party services load with your homepage (Intercom, Google Tag Manager and Twitter and others), adding 525 KiB and 215 ms of main-thread time.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying CSS.

Your largest element takes 16.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “8 ENVIRONMENTAL METRICS - 1 DEVICE”.

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

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

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

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

pods-back.jpg weighs 592 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.5 MB in 66 requests on a phone: images 2.4 MB (23), scripts 590 KiB (20) and fonts 407 KiB (4). Under 2 MB keeps phones on slow connections fast.

8 images (2.1 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 are downloaded at several times the size a phone draws them, for example pods-front.jpg at 1,800 px wide, shown at 390 px. Resized copies would save about 471 KiB.

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

4 buttons have no accessible name, so screen readers announce just “button”.

4 tap targets are too small or too close together to hit reliably with a finger.

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

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

All page content should be contained by landmarks: 15 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.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 69 characters, so Google will cut it off around 60: “Pillar Technologies - The future of construction site risk management”.

The homepage links to 10 pages on pillar.tech and 9 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://pillar.tech/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://pillar.tech/resources is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://pillar.tech/casestudies, https://pillar.tech/demo, https://pillar.tech/careers, https://pillar.tech/resources and https://pillar.tech/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://pillar.tech/casestudies, https://pillar.tech/demo, https://pillar.tech/careers, https://pillar.tech/resources and https://pillar.tech/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.

https://pillar.tech/demo and https://pillar.tech/careers 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 5 pages linked from your homepage and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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.

The homepage carries about 395 words of visible text.

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