gotenna.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Facebook and others), adding 6.4 MB and 730 ms of main-thread time.

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

Shopify costs a phone 13 ms of main-thread work and 4.9 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.

Google Tag Manager costs a phone 428 ms of main-thread work and 793 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.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

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

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

A phone's processor spends 2.5 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

ZenDesk costs a phone 100 ms of main-thread work and 386 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 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

8 long tasks block the main thread while loading, the longest for 126 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).

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 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

6 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 95 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.4 MB in 213 requests on a phone: media 4.8 MB (2), images 3.6 MB (37) and scripts 2.1 MB (67). Under 2 MB keeps phones on slow connections fast.

100925_gTForterra_header.jpg weighs 542 KiB. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example 100925_gTForterra_header.jpg at 1,263 px wide, shown at 346 px. Resized copies would save about 932 KiB.

12 images (2.6 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.

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

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

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

There are 6 <h1> headlines (“We're moving to forterra.com”, “goTenna + Rain Technology Solutions” and “Forterra acquires goTenna.”). One clear main headline is easier for people and search engines.

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

The homepage links to 47 pages on gotenna.com and 71 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/pages/contact-us and /pages/sdk all use the title “Contact Us | goTenna Pro”. Search engines can't tell which page to show for a search, so each competes with the others.

/pages/product-updates-form, /pages/everywhere, /blogs/newsroom and /pages/testimonials have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/contact-us and /pages/sdk use the same meta description. A description written for each page earns more clicks.

/pages/product-updates-form, /blogs/newsroom, /pages/testimonials, /pages/contact-us, /blogs/newsroom/gotenna-awarded-22-3m-to-increase-mission-effectiveness-by-delivering-end-to-end-off-grid-connectivity-through-ruggedized-mobile-mesh-networks and /blogs/newsroom/gotenna-awarded-second-u-s-air-force-contract-to-provide-broad-mesh-network-performance-and-security-insights and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

HSTS is set, but max-age is 91 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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

gotenna.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

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

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

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: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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 12 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.