Website review, no card needed
ihatestevensinger.com website review
Visit site (opens in a new tab)Reviewed 20 November 202643 issues · 94 checks
This review found 43 issues worth fixing on ihatestevensinger.com, 14 of them high impact, across 94 checks. The most urgent: hcaptcha.com adds 2.4 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76C- #75,864 of 125,176 reviewed websitesbeats 35%
- #48,442 of 70,122 online storesbeats 26%
- #45,867 of 63,723 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
| Nov 14, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 159 ms |
| Jun 6, 2026 | 162 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 177 ms |
| Jun 27, 2026 | 182 ms |
| Jul 4, 2026 | 188 ms |
| Jul 11, 2026 | 197 ms |
| Jul 18, 2026 | 202 ms |
| Jul 25, 2026 | 204 ms |
| Aug 1, 2026 | 197 ms |
| Aug 8, 2026 | 194 ms |
| Aug 15, 2026 | 191 ms |
| Aug 22, 2026 | 188 ms |
| Aug 29, 2026 | 188 ms |
| Sep 5, 2026 | 193 ms |
| Sep 12, 2026 | 195 ms |
| Sep 19, 2026 | 195 ms |
| Sep 26, 2026 | 187 ms |
| Oct 3, 2026 | 181 ms |
| Oct 10, 2026 | 174 ms |
| Oct 17, 2026 | 170 ms |
| Oct 24, 2026 | 175 ms |
| Oct 31, 2026 | 177 ms |
| Nov 7, 2026 | 171 ms |
| Nov 14, 2026 | 171 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
How it loaded on a phone
1.0 s
2.0 s
3.0 s
4.0 s
5.1 s
6.1 s
7.1 s
8.1 s
Speed
hcaptcha.com adds 2.4 s
2.4 shcaptcha.com costs a phone 2.4 s of main-thread work and 5.4 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.
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.4 s
A phone's processor spends 9.4 s on main-thread work while loading, 5.6 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 (hcaptcha.com, Google Tag Manager and Yotpo and others), adding 7.7 MB and 3.7 s of main-thread time.
Reduce unused JavaScript
300 ms · 2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Improve image delivery
750 ms · 845 KiB26 images could be 845 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Use efficient cache lifetimes
300 ms · 1.1 MB49 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Google Tag Manager adds 528 ms
528 msGoogle Tag Manager costs a phone 528 ms of main-thread work and 845 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
300 ms · 89 KiBAbout 89 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 321 ms. During a long task the page ignores taps.
2,903 HTML elements
The page has 2,903 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Duplicated JavaScript
273 KiB273 KiB JavaScript is shipped twice across bundles.
Yotpo adds 165 ms
165 msYotpo costs a phone 165 ms of main-thread work and 645 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.
Legacy JavaScript
112 KiBPolyfills for old browsers add 112 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
31 KiB31 KiB could be saved by minifying JavaScript.
Minify CSS
9 KiB9 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: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 22.2 s
22.2 sVisually, the page fills in at 22.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 77.5 s
77.5 sThe page becomes fully interactive after 77.5 s. Good is under 3.8 s.
Largest Contentful Paint: 9.0 s
9.0 sYour largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Limited edition Harry Potter gold and platinum roses shown …”.
Total Blocking Time: 1.8 s
1.8 sScripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.148
0.148The layout shifts by 0.148 while loading, so content jumps under the reader's thumb. Good is under 0.1.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 159 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 184 ms
184 msReal visitors wait 184 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 597 ms
597 msReal visitors wait 597 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 13.7 MB in 495 requests
13.7 MBYour homepage downloads 13.7 MB in 495 requests on a phone: scripts 7.6 MB (137), HTML 2.6 MB (14) and images 1.9 MB (95). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
promo-tablet.png 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).
2 images below the first screen load straight away
2 images further down the page (97 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.9 g of CO₂ per visit
3.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.88 g of CO₂e: 465.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (20 elements)
All page content should be contained by landmarks: 20 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.
9 form fields without a label
9 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA tooltip elements do not have accessible names.
ARIA tooltip elements do not have accessible names. (1 element).
ARIA role should be appropriate for the element (5 elements)
ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 148 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 3 problems
Structured data found (WebSite) but with 3 problems, for example “WebSite: missing name”.
No XML sitemap
No XML sitemap at https://www.ihatestevensinger.com/sitemap.xml, so Google discovers your pages only by following links.
14 links crawlers can't follow
14 links have no real href, so search engines can't follow them.
282 internal links, 15 external
The homepage links to 282 pages on ihatestevensinger.com and 15 external pages.
5 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Browse Steven's collection of fine diamond jewelry, engagement rings, wedding bands, necklaces, gold-dipped roses, brac…”.
Title: 45 characters
Your title is a healthy 45 characters: “I Hate Steven Singer – Steven Singer Jewelers”.
Canonical URL set
The canonical URL is https://www.ihatestevensinger.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.
AI search readiness
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,159 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ihatestevensinger.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.ihatestevensinger.com/pages/most-loved-look-book-2027 has no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://www.ihatestevensinger.com/collections/engagement-rings, https://www.ihatestevensinger.com/collections/anniversary-gifts, https://www.ihatestevensinger.com/pages/the-steven-singer-guarantee, https://www.ihatestevensinger.com/pages/careers, https://www.ihatestevensinger.com/pages/charity and https://www.ihatestevensinger.com/pages/history and 3 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 124 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
1 broken image
1 image failed to load on a phone, for example https://jelly.mdhv.io/v1/star.gif?pid=Xrs4mMGWQ0R37mNpVMfMcbgWDjQi&src=mh&evt=hi.
21 small tap targets
21 of 55 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 691 words of copy
The homepage carries about 691 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Buy Now, Pay Later Options Available” and “SHOP HARRY POTTER™ REAL ROSES”.
28 calls to action
The homepage has 28 calls to action, for example “SHOP ENGAGEMENT”, “SHOP WEDDING BANDS” and “SHOP TOP GIFTS”.
11 short forms
11 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 1 customer or partner logo and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Hotjar and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
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
12 trackers load before any consent
12Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 7 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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies, 2 of them by other companies (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.
71 other companies contacted
Loading the homepage contacts 71 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 ihatestevensinger.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Zepto Product Personalizer · Hulk Form Builder · Yotpo Product Reviews · Helium Customer Fields · Klaviyo Email Marketing Sms · Timesact Pre Order · verifypass.com · breadgateway.net · rechargecdn.com · gorgias.chat · amazonaws.com · 9gtb.com · Swym Wishlist Plus
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
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Shopify
Hiring
- Hiring
- 3 open roles
- Teams
- Customer Service (2), Production (1)
- Job board
- applicantpro
Company
- Headquarters
- Philadelphia
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on ihatestevensinger.com, including 20 speed issues and 4 SEO issues. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.