radianttech.net website review

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

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

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

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

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Google Maps and others), adding 1.2 MB and 634 ms of main-thread time.

Google CDN costs a phone 296 ms of main-thread work and 734 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.6 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,526 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

32 KiB could be saved by minifying JavaScript.

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

18 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 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We’re Radiant Technology Group, Inc. where innovation meets…”. Most of its time is element render delay (9.7 s).

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

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

The first text or image appears after 3.9 s on a phone. Good is under 1.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.

Your homepage downloads 7.3 MB in 145 requests on a phone: images 3.4 MB (17), scripts 1.5 MB (65) and other files 1.5 MB (20). Under 2 MB keeps phones on slow connections fast.

3 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.

4 images (1.9 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.

3 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example 1.jpeg at 600 px wide, shown at 44 px. Resized copies would save about 75 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 2.06 g of CO₂e: 247.3 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.

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

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

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 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.

25 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 skip levels (h2 → h6, h2 → h4 and h3 → h6), which makes the page harder to scan with a screen reader.

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

Your title is only 25 characters: “Home - Radiant Technology”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 99 pages on radianttech.net and 11 external pages.

There is no https://radianttech.net/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://radianttech.net/blog, https://radianttech.net/blog/category/news and https://radianttech.net/blog/category/videos have no meta description, so Google writes the search snippet from whatever text it finds.

https://radianttech.net/collaboration, https://radianttech.net/digital-signage, https://radianttech.net/services, https://radianttech.net/smart-airports, https://radianttech.net/integrated-operations-centers and https://radianttech.net/manufacturing and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://radianttech.net/digital-signage, https://radianttech.net/services, https://radianttech.net/smart-airports, https://radianttech.net/integrated-operations-centers, https://radianttech.net/manufacturing and https://radianttech.net/medical-solutions and 2 others took over 3 s to send their HTML from our server.

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

13 of 18 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 “%c%d font-size:0;color:transparent NaN”.

Chrome logged issues while loading the page (“Mixed content”).

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 8 fields (4 required). Every extra field lowers completion.

The homepage carries about 724 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, 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 3 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.