Website review, no card needed
angelizconceptstore.com website review
Visit site (opens in a new tab)Reviewed 16 November 202646 issues · 84 checks
This review found 46 issues worth fixing on angelizconceptstore.com, 19 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
65DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.9 s
1.8 s
2.7 s
3.7 s
4.6 s
5.5 s
6.4 s
7.3 s
Speed
Improve image delivery
2.9 s · 40.0 MB28 images could be 40.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.
Reduce unused JavaScript
5.0 s · 985 KiBAbout 985 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.
Use efficient cache lifetimes
2.1 s · 357 KiB12 files are served with short cache lifetimes, so returning visitors download them again (357 KiB).
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and smartarget.online and others), adding 1.6 MB and 1.3 s of main-thread time.
YouTube adds 660 ms
660 msYouTube costs a phone 660 ms of main-thread work and 992 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
450 ms · 122 KiBAbout 122 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 351 ms
351 msGoogle Tag Manager costs a phone 351 ms of main-thread work and 192 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.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
300 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
2,508 HTML elements
The page has 2,508 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 245 ms. During a long task the page ignores taps.
Font display
50 msWeb 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.
1 checks passed
Server response: 457 ms
457 msYour server sent the HTML in 457 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 20.6 s
20.6 sYour largest element takes 20.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “. .”.
Time to Interactive: 20.8 s
20.8 sThe page becomes fully interactive after 20.8 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 642 ms
642 msScripts block taps and scrolling for 642 ms in total while the page loads. Good is under 200 ms.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.085
0.085The layout barely moves while loading (CLS 0.085, good is under 0.1).
Images and page weight
Page weight: 42.5 MB in 93 requests
42.5 MBYour homepage downloads 42.5 MB in 93 requests on a phone: images 40.7 MB (32), scripts 1.4 MB (20) and fonts 187 KiB (3). Under 2 MB keeps phones on slow connections fast.
19 images far larger than shown
3.5 MB19 images are downloaded at several times the size a phone draws them, for example 90511431.png at 1,800 px wide, shown at 155 px. Resized copies would save about 3.5 MB.
An image on the first screen is lazy-loaded
15922452.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).
1 image in older formats
1 image (157 KiB) is 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 (201 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 12.0 g of CO₂ per visit
12.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 12.04 g of CO₂e: 1444.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
41 buttons without a name
41 buttons have no accessible name, so screen readers announce just “button”.
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.
<svg> elements with an img or image role must have alternative text (2 elements)
<svg> elements with an img or image role must have alternative text: 2 elements on the page fail this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
53 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: 53 passed and 9 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.
Title is long (115 characters)
Your title is 115 characters, so Google will cut it off around 60: “Angeliz Baby Gift Set Hamper for newborn & baby shower | Our hampers come with free stand…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (240 characters)
Your meta description is 240 characters; Google truncates after about 160, so the end of your pitch is cut.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
119 internal links, 5 external
The homepage links to 119 pages on angelizconceptstore.com and 5 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.angelizconceptstore.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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.angelizconceptstore.com/sitemap.xml.
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.
No llms.txt
There is no https://www.angelizconceptstore.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.
2 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,341 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://www.angelizconceptstore.com/collections/all, https://www.angelizconceptstore.com/collections/sales, https://www.angelizconceptstore.com/collections/baby-hampers, https://www.angelizconceptstore.com/collections/premium-baby-hamper, https://www.angelizconceptstore.com/collections/cake-box-hamper and https://www.angelizconceptstore.com/collections/net-basket-hamper and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages slow to respond
https://www.angelizconceptstore.com/collections/unisex-hamper, https://www.angelizconceptstore.com/collections/twins-gift-set and https://www.angelizconceptstore.com/collections/flower-girl took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 74 found) and read each the way a search engine does.
6 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.
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
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://store-themes.easystore.co/857981/themes/289981/assets/base.css?t=1793041271' from …”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
39 of 45 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 9 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
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 1,018 words of copy
The homepage carries about 1,018 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP”.
12 calls to action
The homepage has 12 calls to action, for example “Subscribe”, “Shop Now” and “ORDER & DELIVERY”.
3 short forms
3 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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
13Opening the homepage sets 13 cookies, 1 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.
20 other companies contacted
Loading the homepage contacts 20 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 angelizconceptstore.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on angelizconceptstore.com, including 17 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.