Website review, no card needed

Plug logo

plug.tech website review

Visit site (opens in a new tab)Reviewed 4 November 202624 issues · 58 checks

This review found 24 issues worth fixing on plug.tech, 10 of them high impact, across 58 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Plug

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
6.0 s3.8 sMay 16Oct 315.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.4 s
May 23, 20264.4 s
May 30, 20264.3 s
Jun 6, 20264.2 s
Jun 13, 20264.1 s
Jun 20, 20264.1 s
Jun 27, 20264.2 s
Jul 4, 20264.4 s
Jul 11, 20264.5 s
Jul 18, 20264.4 s
Jul 25, 20264.3 s
Aug 1, 20264.4 s
Aug 8, 20264.4 s
Aug 15, 20264.6 s
Aug 22, 20264.6 s
Aug 29, 20264.6 s
Sep 5, 20264.6 s
Sep 12, 20264.7 s
Sep 19, 20264.8 s
Sep 26, 20265.2 s
Oct 3, 20265.5 s
Oct 10, 20265.6 s
Oct 17, 20265.7 s
Oct 24, 20265.4 s
Oct 31, 20265.2 s
Real-visitor tap response (INP)75th percentile, phones
1.2 s741 msMay 16Oct 311.1 s
Show as table
DateReal-visitor tap response (INP)
May 16, 2026940 ms
May 23, 2026914 ms
May 30, 2026900 ms
Jun 6, 2026896 ms
Jun 13, 2026918 ms
Jun 20, 2026939 ms
Jun 27, 2026971 ms
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 2026967 ms
Jul 25, 2026892 ms
Aug 1, 2026830 ms
Aug 8, 2026794 ms
Aug 15, 2026806 ms
Aug 22, 2026819 ms
Aug 29, 2026831 ms
Sep 5, 2026840 ms
Sep 12, 2026838 ms
Sep 19, 2026981 ms
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

7 to fix33
  • Fails Core Web Vitals for real visitors

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

  • Real-user LCP: 5.2 s

    5.2 s

    Real visitors wait 5.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 1.2 s

    1.2 s

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Tap response (INP) got 22% slower for real visitors

    +22%

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

  • Largest content (LCP) got 20% slower for real visitors

    +20%

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

1 checks passed
  • Real-user CLS: 0.06

    0.06

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

Images and page weight

3 to fix53
  • Page weight: 4.6 MB

    4.6 MB

    Your homepage downloads 4.6 MB on a phone, 993 KiB of it images (21%). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    PLUG_SALE_BANNER_3.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    428 KiB

    1 image is downloaded at several times the size a phone draws it, for example ZelgcfjZ3-G_pJ6retzyZ.png at 1,024 px wide, shown at 60 px. Resized copies would save about 428 KiB.

  • 1 image in older formats

    1 image (442 KiB) is 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.

  • About 1.3 g of CO₂ per visit

    1.30 g

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

Accessibility

6 to fix92
  • Images must have alternative text (3 elements)

    Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 8 tap targets too small

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (12 elements)

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fix95
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Black Friday Came Early”). One clear main headline is easier for people and search engines.

  • 778 internal links, 6 external

    The homepage links to 778 pages on plug.tech and 6 external pages.

7 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “Shop 1,000+ certified pre-owned iPhones, Samsung, MacBooks & more. Fully unlocked, 30-day returns. Free shipping. Start…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Certified Pre-Owned iPhones & Tech - Up to 60% Off | Plug”.

  • Canonical URL set

    The canonical URL is https://www.plug.tech/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.plug.tech/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.plug.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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (5,205 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.plug.tech/collections/all and https://www.plug.tech/products/iphone-14-purple-128gb-unlocked have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://www.plug.tech/collections/all, https://www.plug.tech/collections/black-friday-deals, https://www.plug.tech/products/iphone-14-purple-128gb-unlocked, https://www.plug.tech/products/iphone-15-black-128gb-unlocked, https://www.plug.tech/products/samsung-galaxy-s24-ultra-5g-256gb-titanium-black-unlocked and https://www.plug.tech/products/ipad-2021-9th-gen-10-2-64gb-space-gray-wifi-only and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fix78
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=175019212&tm=gtm002&Ver=2&mid=b99bdd24-71ee-44d6-ab52-96aa2f23c7c9&bo=1&sid=905d4890d80f11f1929e0105ec658d50&vid=905d8c00d80f11f1ba6bd5564c33b3c4&vids=1&msclkid=N&gtm_.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin”.

2 checks passed
  • Tap targets are thumb-sized

    34 of 35 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

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

  • No direct contact details

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

  • About 2,198 words of copy

    The homepage carries about 2,198 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop” and “Shop Early Black Friday”.

  • 31 calls to action

    The homepage has 31 calls to action, for example “Shop Now”, “Shop” and “Shop All iPhones”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and PostHog.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.

  • 49 cookies set on arrival

    49

    Opening the homepage sets 49 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 53 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at plug.tech, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager | PostHog
Hosting
Shopify

Hiring

Hiring
2 open roles
Teams
Employees (2)
Job board
bamboohr

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on plug.tech, including 7 speed issues, 1 SEO issue and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25