2gig.com website review

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

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

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

About 679 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.8 s faster on a phone.

524 KiB could be saved by minifying CSS.

8 third-party services load with your homepage (Google Tag Manager, pcdn.co and ShareThis and others), adding 9.4 MB and 870 ms of main-thread time.

pcdn.co costs a phone 237 ms of main-thread work and 7.8 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.

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

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

Google Tag Manager costs a phone 360 ms of main-thread work and 794 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.4 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Vimeo costs a phone 39 ms of main-thread work and 524 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.

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

15 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 38.4 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 39.3 s. Good is under 3.8 s.

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

5 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-17, real Chrome visitors' tap response (inp) went from 84 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 9.5 MB in 143 requests on a phone: images 6.3 MB (42), scripts 1.8 MB (36) and stylesheets 700 KiB (12). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Untitled-design-12.jpg at 1,800 px wide, shown at 360 px. Resized copies would save about 70 KiB.

3 images (156 KiB) 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 (156 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 2.68 g of CO₂e: 322.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

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

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

There are 5 <h1> headlines (“GC Touch”, “Extended Range E+ Sensors” and “Nothing is More Unique Than You”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

5 links have no real href, so search engines can't follow them.

The homepage links to 43 pages on 2gig.com and 24 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.

There is no /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.

/blog/edge-vs-cloud-computing, /blog/top-5-safety-tips-for-fire-prevention-month and /blog/how-2gig-security-systems-help-you-sell-in-every-room-of-the-house declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, /blog/edge-vs-cloud-computing, /blog/top-5-safety-tips-for-fire-prevention-month and /blog/how-2gig-security-systems-help-you-sell-in-every-room-of-the-house all use the title “Smart Home Security & Monitoring | 2GIG”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/products, /resources, /helpcenter, /solutions, /dealer and /become-a-dealer and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

/2gigedge-security-automation-panel and /gctouch use the same meta description. A description written for each page earns more clicks.

/2gigedge-security-automation-panel, /gctouch, /products, /resources, /security-dealers-and-installers-near-me and /helpcenter and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

/helpcenter has 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 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://2gig.com' has been blocked by CORS…”.

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

http://2gig.com does not redirect to https, so some visitors land on the insecure version.

1 link to other sites is dead, for example https://dev-2gig-nsc.pantheonsite.io/products/ (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://na.niceforyou.com/.

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.

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

2gig.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.

2gig.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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

2gig.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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, Hotjar and Microsoft Clarity (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 18 cookies, 2 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.