Website review, no card needed

phipsistore.com logo

phipsistore.com website review

Visit site (opens in a new tab)Reviewed 11 November 202634 issues · 82 checks

This review found 34 issues worth fixing on phipsistore.com, 10 of them high impact, across 82 checks. The most urgent: improve image delivery. 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
3.0 s773 msMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.7 s
May 30, 20262.7 s
Sep 5, 20261.0 s
Sep 12, 20261.6 s
Sep 19, 20261.9 s
Sep 26, 20262.3 s
Oct 3, 20262.1 s
Oct 31, 20261.0 s
Nov 7, 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

Full-page screenshot of phipsistore.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. phipsistore.com at 0.7 s0.7 s
  2. phipsistore.com at 1.4 s1.4 s
  3. phipsistore.com at 2.1 s2.1 s
  4. phipsistore.com at 2.8 s2.8 s
  5. phipsistore.com at 3.5 s3.5 s
  6. phipsistore.com at 4.2 s4.2 s
  7. phipsistore.com at 4.9 s4.9 s
  8. phipsistore.com at 5.6 s5.6 s

Speed

10 to fix65
  • Improve image delivery

    1.3 s · 14.3 MB

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

  • Use efficient cache lifetimes

    1.6 MB

    27 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Google CDN and Shopify and others), adding 1.7 MB and 878 ms of main-thread time.

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    150 ms · 589 KiB

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

  • Render-blocking requests

    700 ms

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

  • Main-thread work: 3.5 s

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

  • Klaviyo adds 259 ms

    259 ms

    Klaviyo costs a phone 259 ms of main-thread work and 509 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 adds 162 ms

    162 ms

    Shopify costs a phone 162 ms of main-thread work and 413 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 CDN adds 171 ms

    171 ms

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

  • 5 long tasks on the main thread

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

  • Minify JavaScript

    73 KiB

    73 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    39 KiB

    About 39 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    18 KiB

    18 KiB JavaScript is shipped twice across bundles.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 8 ms

    8 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 9.5 s

    9.5 s

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

  • Time to Interactive: 28.8 s

    28.8 s

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

  • Speed Index: 6.6 s

    6.6 s

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

  • Total Blocking Time: 234 ms

    234 ms

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

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 0.8 s

    0.8 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 513 ms

    513 ms

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

  • Largest content (LCP) got 61% faster for real visitors

    -61%

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

2 to fix60
  • Page weight: 18.6 MB in 305 requests

    18.6 MB

    Your homepage downloads 18.6 MB in 305 requests on a phone: images 15.8 MB (55), scripts 1.7 MB (133) and other files 698 KiB (84). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    28 KiB

    3 images are downloaded at several times the size a phone draws them, for example HR26-MobileBanner-52.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 28 KiB.

  • 7 images below the first screen load straight away

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

  • About 5.3 g of CO₂ per visit

    5.27 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 9091
  • 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.

  • Frames without titles

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

  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

  • 14 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 48 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 9276
  • No H1 headline

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

  • Title is short (28 characters)

    Your title is only 28 characters: “Phi Kappa Psi Official Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (310 characters)

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

  • 8 links crawlers can't follow

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

  • 137 internal links, 6 external

    The homepage links to 137 pages on phipsistore.com and 6 external pages.

5 checks passed
  • Canonical URL set

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

  • 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.phipsistore.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.phipsistore.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: 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 (466 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 3 pages share a title

    /, https://www.phipsistore.com/apps/wishlist and https://www.phipsistore.com/a/bundles/brotherhood-basics-bundle-f17p all use the title “Phi Kappa Psi Official Store”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.phipsistore.com/apps/wishlist, https://www.phipsistore.com/a/bundles/brotherhood-basics-bundle-f17p, https://www.phipsistore.com/collections/golf-collection, https://www.phipsistore.com/collections/limited-drops and https://www.phipsistore.com/collections/value-collection have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.phipsistore.com/a/bundles/brotherhood-basics-bundle-f17p has 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 60 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    6 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-bundler.nice-team.net/app/css/promotions-style.css?shop=phi-kappa-psi-official…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 13 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • 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 373 words of copy

    The homepage carries about 373 words of visible text.

3 checks passed
  • 15 calls to action

    The homepage has 15 calls to action, for example “Sweetheart Shop”, “Bulk Order & Save!” and “Start A Custom Order”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 13 cookies set on arrival

    13

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

  • 33 other companies contacted

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

Apps on your store

Your storefront loads 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Bundler Bundles App · Wishlist Fade My Wishlist · Reamaze Live Chat Helpdesk · Returngo Returns Exchanges · Google Youtube · Gorgias Live Chat Helpdesk · Gsc Instagram Feed · Klaviyo Email Marketing Sms · Selleasy · nice-team.net

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on phipsistore.com, including 14 speed issues, 4 SEO issues and 3 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