Website review, no card needed

stselectronicrecyclinginc.com logo

stselectronicrecyclinginc.com website review

Visit site (opens in a new tab)Reviewed 25 October 202640 issues · 91 checks

This review found 40 issues worth fixing on stselectronicrecyclinginc.com, 16 of them high impact, across 91 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

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

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

Real-visitor load time (LCP)75th percentile, phones
2.5 s1.8 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.9 s
May 9, 20261.9 s
May 16, 20262.0 s
May 23, 20262.2 s
May 30, 20262.1 s
Jun 6, 20262.2 s
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.1 s
Sep 19, 20262.2 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
98 ms74 msMay 2Oct 1780 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202679 ms
May 9, 202679 ms
May 16, 202679 ms
May 23, 202679 ms
May 30, 202680 ms
Jun 6, 202681 ms
Jun 13, 202680 ms
Jun 20, 202679 ms
Jun 27, 202678 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202680 ms
Jul 25, 202680 ms
Aug 1, 202677 ms
Aug 8, 202679 ms
Aug 15, 202683 ms
Aug 22, 202687 ms
Aug 29, 202695 ms
Sep 5, 202695 ms
Sep 12, 202688 ms
Sep 19, 202687 ms
Sep 26, 202682 ms
Oct 3, 202680 ms
Oct 10, 202683 ms
Oct 17, 202680 ms

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

Full-page screenshot of stselectronicrecyclinginc.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. stselectronicrecyclinginc.com at 0.7 s0.7 s
  2. stselectronicrecyclinginc.com at 1.5 s1.5 s
  3. stselectronicrecyclinginc.com at 2.2 s2.2 s
  4. stselectronicrecyclinginc.com at 3.0 s3.0 s
  5. stselectronicrecyclinginc.com at 3.7 s3.7 s
  6. stselectronicrecyclinginc.com at 4.4 s4.4 s
  7. stselectronicrecyclinginc.com at 5.2 s5.2 s
  8. stselectronicrecyclinginc.com at 5.9 s5.9 s

Speed

12 to fix30
  • Render-blocking requests

    3.2 s

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

  • Google Tag Manager adds 1.4 s

    1.4 s

    Google Tag Manager costs a phone 1.4 s of main-thread work and 499 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 7.9 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, termly.io and elfsightcdn.com and others), adding 1.9 MB and 3.7 s of main-thread time.

  • Reduce unused JavaScript

    750 ms · 963 KiB

    About 963 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Use efficient cache lifetimes

    750 ms · 761 KiB

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

  • termly.io adds 539 ms

    539 ms

    termly.io costs a phone 539 ms of main-thread work and 162 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.

  • elfsightcdn.com adds 510 ms

    510 ms

    elfsightcdn.com costs a phone 510 ms of main-thread work and 340 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 Maps adds 479 ms

    479 ms

    Google Maps costs a phone 479 ms of main-thread work and 426 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 on the main thread

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

  • Google CDN adds 433 ms

    433 ms

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

  • Reduce unused CSS

    150 ms · 23 KiB

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

  • Improve image delivery

    117 KiB

    3 images could be 117 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    50 ms

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 87 ms

    87 ms

    Your server sent the HTML in 87 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 10.6 s

    10.6 s

    Your largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Certified IT asset disposition for enterprises, healthcare …”.

  • Time to Interactive: 19.2 s

    19.2 s

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

  • Total Blocking Time: 2.9 s

    2.9 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Speed Index: 7.5 s

    7.5 s

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

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

    +26%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

4 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 79 ms

    79 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.066

    0.066

    The layout barely moves while loading (CLS 0.066, good is under 0.1).

Images and page weight

5 to fix33
  • 1 image over 500 KB

    r2v3logo.png weighs 864 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    767 KiB

    1 image is downloaded at several times the size a phone draws it, for example r2v3logo.png at 1,254 px wide, shown at 140 px. Resized copies would save about 767 KiB.

  • Page weight: 3.5 MB in 101 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 101 requests on a phone: scripts 2.0 MB (45), images 1.1 MB (13) and fonts 223 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (895 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.

  • 2 images below the first screen load straight away

    2 images further down the page (885 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.98 g

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

Accessibility

6 to fixGoogle 8193
  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 3 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

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

  • 13 form fields without a label

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

  • 2 links without text

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

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 56 automated accessibility rules passed

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

SEO

2 to fixGoogle 10089
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “R2/NAID Certified Electronics Recycling | Free Nationwide Pickup | STS”.

  • Structured data has 1 problem

    Structured data found (Article, BreadcrumbList, FAQPage and HowTo) but with 1 problem, for example “Organization: missing name”.

  • 119 internal links, 5 external

    The homepage links to 119 pages on stselectronicrecyclinginc.com and 5 external pages.

6 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Free electronics recycling pickup for businesses & schools nationwide. Get paid for high-value IT assets. R2/NAID certi…”.

  • One H1 headline

    Your main headline reads: “IT asset disposition, in writing.”.

  • Canonical URL set

    The canonical URL is https://www.stselectronicrecyclinginc.com/.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.stselectronicrecyclinginc.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.stselectronicrecyclinginc.com/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: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix98
  • 4 pages share a meta description

    https://www.stselectronicrecyclinginc.com/CONTACT-STS-PAGE, https://www.stselectronicrecyclinginc.com/testimonials, https://www.stselectronicrecyclinginc.com/services/computer-lease-buyout and https://www.stselectronicrecyclinginc.com/services/mar-program use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343140323&Ver=2&mid=2b7f6455-0630-41fd-9d8b-b8d20ed66531&bo=1&sid=2b0c9410d02a11f1b668b7ecdeca8eab&vid=2b0cc7c0d02a11f18bcd677df6531c33&vids=1&msclkid=N&pi=918639831&l.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'lang')”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Thin social proof

    Social proof on the homepage: 8 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 11-field form

    Your longest form asks for 11 fields (3 required). Every extra field lowers completion.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 2,464 words of copy

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Free Quote” and “Call Us”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Free Quote”, “Call Us” and “Call Center Industry”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

  • 14 cookies set on arrival

    14

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

  • 29 other companies contacted

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

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) loads with the page.

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 stselectronicrecyclinginc.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
Joomla
Framework
jQuery
Analytics
Google Analytics
Hosting
HostMonster;Incapsula;Unified Layer;Black Lotus

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on stselectronicrecyclinginc.com, including 22 speed issues, 2 SEO issues 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