Website review, no card needed

simplyframed.com logo

simplyframed.com website review

Visit site (opens in a new tab)Reviewed 6 November 202639 issues · 87 checks

This review found 39 issues worth fixing on simplyframed.com, 14 of them high impact, across 87 checks. The most urgent: google Tag Manager adds 2.2 s. 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.2 s1.6 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.9 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
141 ms90 msMay 16Oct 31121 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202696 ms
May 23, 2026103 ms
May 30, 202699 ms
Jun 6, 202696 ms
Jun 13, 202697 ms
Jun 20, 2026100 ms
Jun 27, 2026102 ms
Jul 4, 2026112 ms
Jul 11, 2026108 ms
Jul 18, 2026115 ms
Jul 25, 2026113 ms
Aug 1, 2026112 ms
Aug 8, 2026113 ms
Aug 15, 2026112 ms
Aug 22, 2026119 ms
Aug 29, 2026122 ms
Sep 5, 2026135 ms
Sep 12, 2026128 ms
Sep 19, 2026124 ms
Sep 26, 2026113 ms
Oct 3, 2026104 ms
Oct 10, 2026113 ms
Oct 17, 2026112 ms
Oct 24, 2026117 ms
Oct 31, 2026121 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 simplyframed.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. simplyframed.com at 0.4 s0.4 s
  2. simplyframed.com at 0.8 s0.8 s
  3. simplyframed.com at 1.1 s1.1 s
  4. simplyframed.com at 1.5 s1.5 s
  5. simplyframed.com at 1.9 s1.9 s
  6. simplyframed.com at 2.3 s2.3 s
  7. simplyframed.com at 2.6 s2.6 s
  8. simplyframed.com at 3.0 s3.0 s

Speed

10 to fix42
  • Google Tag Manager adds 2.2 s

    2.2 s

    Google Tag Manager costs a phone 2.2 s of main-thread work and 2.0 MB 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: 42

    42/100

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

  • Main-thread work: 6.6 s

    A phone's processor spends 6.6 s on main-thread work while loading, 3.4 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, Hubspot and Privy and others), adding 3.1 MB and 3.0 s of main-thread time.

  • Reduce unused JavaScript

    1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    150 ms · 768 KiB

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

  • Render-blocking requests

    900 ms

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

  • 20 long tasks on the main thread

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

  • Hubspot adds 257 ms

    257 ms

    Hubspot costs a phone 257 ms of main-thread work and 320 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.

  • Privy adds 185 ms

    185 ms

    Privy costs a phone 185 ms of main-thread work and 296 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.

  • Improve image delivery

    150 ms · 71 KiB

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

  • Document request latency

    153 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 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

    5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 52 ms

    52 ms

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

Core Web Vitals

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

  • Time to Interactive: 40.2 s

    40.2 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 5.3 s

    5.3 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

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

    +20%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 96 ms to 121 ms 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.

6 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 117 ms

    117 ms

    Real visitors wait 117 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.

  • Real-user FCP: 1.5 s

    1.5 s

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

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

    -11%

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

  • Cumulative Layout Shift: 0.012

    0.012

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

Images and page weight

1 to fix70
  • Page weight: 7.1 MB in 243 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 243 requests on a phone: scripts 3.5 MB (89), other files 2.2 MB (92) and fonts 777 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

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

  • 1 image below the first screen load straight away

    1 image further down the page (31 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.0 g of CO₂ per visit

    2.00 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8890
  • 25 text elements with low contrast

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

  • 11 tap targets too small

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

  • 6 images without alt text

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

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 links without text

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

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

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • No structured data

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 59 internal links, 6 external

    The homepage links to 59 pages on simplyframed.com and 6 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Selection of high quality wood gallery frames at discount prices. Mail-In Service. Best way to get art, photos, posters…”.

  • One H1 headline

    Your main headline reads: “Simply Framed”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Simply Framed - Custom frames, made simple”.

  • Canonical URL set

    The canonical URL is https://simplyframed.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://simplyframed.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://simplyframed.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix70
  • 2 linked pages hidden from search

    https://simplyframed.com/design/SVpfATaaFRgxbkMSfMZ1x5MBpMMeACsSPsHHwBKsPPmAW8AH10 and https://simplyframed.com/design/SVpfATaaFRgxbkMSfMZ1x5MBpMMeACsSPsHHwPPmAW8AH10 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share 2 titles

    https://simplyframed.com/design/SVpfATaaFRgxbkMSfMZ1x5MBpMMeACsSPsHHwBKsPPmAW8AH10 and https://simplyframed.com/design/SVpfATaaFRgxbkMSfMZ1x5MBpMMeACsSPsHHwPPmAW8AH10 all use the title “Simply Framed — Design a Custom Frame”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages without a meta description

    https://simplyframed.com/design/SVpfATaaFRgxbkMSfMZ1x5MBpMMeACsSPsHHwBKsPPmAW8AH10, https://simplyframed.com/trade, https://simplyframed.com/pages/for-business, https://simplyframed.com/pages/for-artists, https://simplyframed.com/pages/for-home and https://simplyframed.com/pages/request-a-quote and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://simplyframed.com/collections, whose canonical is https://simplyframed.com/collections/all. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://simplyframed.com/design/SVpfATaaFRgxbkMSfMZ1x5MBpMMeACsSPsHHwBKsPPmAW8AH10, https://simplyframed.com/collections and https://simplyframed.com/design/SVpfATaaFRgxbkMSfMZ1x5MBpMMeACsSPsHHwPPmAW8AH10 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://simplyframed.com/pages/request-a-quote and https://simplyframed.com/pages/contact-sales have 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.

  • 1 page slow to respond

    https://simplyframed.com/collections took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5510903&Ver=2&mid=84dabdbf-eb26-4b9f-a6af-1eaf83c5b5f7&bo=1&sid=c59f78d0da3011f1b0ad271b0eabce82&vid=c59f90c0da3011f1b509452b7ebbd029&vids=1&msclkid=N&pi=918639831&lg=.

  • 5 small tap targets

    5 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: SearchForm is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

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

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

    The homepage carries about 616 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: “REQUEST A QUOTE”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Start a Frame”, “Request a Quote” and “Learn More”.

  • 3 short forms

    3 short forms (0 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

  • Direct contact links

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

Privacy and tracking

  • 7 trackers load before any consent

    7

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

  • 38 cookies set on arrival

    38

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

  • 40 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 simplyframed.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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Attentive · privy.com · attn.tv · hubapi.com

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
Analytics
Google Tag Manager
Hosting
AWS

Company

Headquarters
Denver

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on simplyframed.com, including 18 speed issues, 2 SEO issues and 1 conversion gap. 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