3rtechnology.com website review

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.

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

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

Your mobile performance score is 19. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (hsappstatic.net, Google Tag Manager and Google CDN and others), adding 3.2 MB and 2.4 s of main-thread time.

hsappstatic.net costs a phone 764 ms of main-thread work and 715 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.

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

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

Google CDN costs a phone 325 ms of main-thread work and 736 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.

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

Google Maps costs a phone 234 ms of main-thread work and 462 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.

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

11 KiB could be saved by minifying JavaScript.

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

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

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

Real visitors wait 244 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

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

Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

Real visitors wait 831 ms for your server to start answering (75th percentile). Good is under 800 ms.

The layout shifts by 0.234 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.4 MB in 457 requests on a phone: scripts 3.6 MB (131), other files 1.8 MB (261) and images 393 KiB (32). Under 2 MB keeps phones on slow connections fast.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (1 element).

There are 3 <h1> headlines (“ITAD Services in Washington and the Pacific North…”, “Certified IT Asset Disposition and Electronics Re…” and “Why We're the Best in the Northwest”). One clear main headline is easier for people and search engines.

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

The homepage links to 180 pages on 3rtechnology.com and 37 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/chromebox-solutions-from-ctl, /pages/ctl-ops-all-in-one-aio-with-chromeos-desktop-computers and /collections/interactive-classroom-displays have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187013548&Ver=2&mid=4422131a-8b45-4ad7-8933-164972b09068&bo=1&sid=2ad3d4a0d7ca11f1a36491b6d241c64b&vid=2ad40580d7ca11f18e52037ed257d094&vids=1&msclkid=N&pi=918639831&l.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) Price Rules is not enabled for this store.”.

3 images are served at too low a resolution for sharp phone screens.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

Opening https://3rtechnology.com goes through 2 redirects before the homepage loads.

2 links go through two or more redirects, for example https://instagram.com/ctldotnet.

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.

ctl.net 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.

ctl.net'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.

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.

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 876 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, HubSpot and LinkedIn Insight and 4 mores (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 19 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 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.