Website review, no card needed

2friendsshopping.com logo

2friendsshopping.com website review

Visit site (opens in a new tab)Reviewed 17 November 202640 issues · 71 checks

This review found 40 issues worth fixing on 2friendsshopping.com, 17 of them high impact, across 71 checks. The most urgent: reduce unused JavaScript. 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
4.4 s4.1 sMay 30Nov 144.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.2 s
Jun 6, 20264.2 s
Jun 13, 20264.2 s
Jun 20, 20264.3 s
Jun 27, 20264.3 s
Jul 4, 20264.3 s
Jul 11, 20264.3 s
Jul 18, 20264.3 s
Jul 25, 20264.3 s
Aug 1, 20264.3 s
Aug 8, 20264.3 s
Aug 15, 20264.3 s
Aug 22, 20264.2 s
Aug 29, 20264.3 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.3 s
Sep 26, 20264.3 s
Oct 3, 20264.3 s
Oct 10, 20264.3 s
Oct 17, 20264.3 s
Oct 24, 20264.3 s
Oct 31, 20264.3 s
Nov 7, 20264.3 s
Nov 14, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
748 ms409 msMay 30Nov 14448 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026623 ms
Jun 6, 2026622 ms
Jun 13, 2026626 ms
Jun 20, 2026633 ms
Jun 27, 2026640 ms
Jul 4, 2026663 ms
Jul 11, 2026692 ms
Jul 18, 2026708 ms
Jul 25, 2026709 ms
Aug 1, 2026688 ms
Aug 8, 2026651 ms
Aug 15, 2026606 ms
Aug 22, 2026562 ms
Aug 29, 2026523 ms
Sep 5, 2026493 ms
Sep 12, 2026476 ms
Sep 19, 2026474 ms
Sep 26, 2026470 ms
Oct 3, 2026463 ms
Oct 10, 2026460 ms
Oct 17, 2026459 ms
Oct 24, 2026461 ms
Oct 31, 2026458 ms
Nov 7, 2026453 ms
Nov 14, 2026448 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 2friendsshopping.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 2friendsshopping.com at 0.5 s0.5 s
  2. 2friendsshopping.com at 1.1 s1.1 s
  3. 2friendsshopping.com at 1.6 s1.6 s
  4. 2friendsshopping.com at 2.2 s2.2 s
  5. 2friendsshopping.com at 2.7 s2.7 s
  6. 2friendsshopping.com at 3.3 s3.3 s
  7. 2friendsshopping.com at 3.8 s3.8 s
  8. 2friendsshopping.com at 4.4 s4.4 s

Speed

5 to fix31
  • Reduce unused JavaScript

    9.7 s · 1.4 MB

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

  • Improve image delivery

    2.8 s · 555 KiB

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

  • Mobile performance score: 31

    31/100

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

  • Main-thread work: 3.8 s

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

  • Google CDN adds 297 ms

    297 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google reCAPTCHA and others), adding 1,024 KiB and 379 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 69 KiB

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

  • Legacy JavaScript

    150 ms · 13 KiB

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

  • 9 long tasks on the main thread

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

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

1 checks passed
  • Server response: 65 ms

    65 ms

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

Core Web Vitals

12 to fix33
  • 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.

  • Real-user LCP: 4.3 s

    4.3 s

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Largest Contentful Paint: 27.0 s

    27.0 s

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

  • Time to Interactive: 27.5 s

    27.5 s

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

  • Speed Index: 12.8 s

    12.8 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Cumulative Layout Shift: 0.303

    0.303

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

  • Real-user INP: 446 ms

    446 ms

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

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

  • Total Blocking Time: 400 ms

    400 ms

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

2 checks passed
  • Real-user CLS: 0.08

    0.08

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

  • Tap response (INP) got 28% faster for real visitors

    -28%

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

Images and page weight

1 to fix33
  • Page weight: 5.2 MB in 143 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 143 requests on a phone: scripts 2.9 MB (81), images 1.5 MB (27) and other files 417 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.48 g

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

Accessibility

4 to fixGoogle 9493
  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 tap targets too small

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

1 checks passed
  • 25 automated accessibility rules passed

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

SEO

6 to fixGoogle 10065
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (9 characters)

    Your title is only 9 characters: “Pinterest”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No XML sitemap

    No XML sitemap at https://www.pinterest.com/v3_sitemaps/ideas_hub_v_expansion_sitemap_batch_2_www.pinterest.com.xml, so Google discovers your pages only by following links.

  • Only 3 internal links

    The homepage links to only 3 pages on your own site, so visitors and crawlers find few routes into the rest of it.

3 checks passed
  • Meta description: 71 characters

    Your meta description is 71 characters: “Discover recipes, home ideas, style inspiration and other ideas to try.”.

  • Canonical URL set

    The canonical URL is https://www.pinterest.com/2FriendsFX/2friendsdesigns-shopify-shots-call-5416544199/shopify-website-examples-by-2fd/.

  • Open Graph tags complete

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

AI search readiness

2 to fix37
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Other pages

3 to fix86
  • 4 pages share a title

    https://www.pinterest.com/2FriendsFX/2friendsdesigns-shopify-shots-call-5416544199/shopify-website-examples-by-2fd, /, https://www.pinterest.com/ideas and https://www.pinterest.com/shopping all use the title “Pinterest”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    /, https://www.pinterest.com/ideas and https://www.pinterest.com/shopping use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    /, https://www.pinterest.com/ideas and https://www.pinterest.com/shopping have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 internal pages checked

    We fetched 3 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 3 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 3 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot use 'in' operator to search for 'addEventListener' in undefined”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 11 words

    The homepage has only about 11 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop” and “Sign up”.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Pinterest Tag (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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 2 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Shopify

Company

Headquarters
Eugene

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 2friendsshopping.com, including 17 speed issues, 6 SEO issues and 5 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