Website review, no card needed
giftsanddec.com website review
Visit site (opens in a new tab)Reviewed 11 November 202655 issues · 95 checks
This review found 55 issues worth fixing on giftsanddec.com, 22 of them high impact, across 95 checks. The most urgent: reduce unused JavaScript. 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 sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 2.9 s |
| Nov 7, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 104 ms |
| May 30, 2026 | 110 ms |
| Jun 6, 2026 | 106 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 95 ms |
| Jul 4, 2026 | 94 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 147 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 150 ms |
| Aug 15, 2026 | 150 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 108 ms |
| Sep 5, 2026 | 114 ms |
| Sep 12, 2026 | 115 ms |
| Sep 19, 2026 | 117 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 123 ms |
| Oct 10, 2026 | 130 ms |
| Oct 17, 2026 | 131 ms |
| Oct 24, 2026 | 131 ms |
| Oct 31, 2026 | 132 ms |
| Nov 7, 2026 | 126 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
3.1 s · 922 KiBAbout 922 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 775 KiB34 files are served with short cache lifetimes, so returning visitors download them again (775 KiB).
Render-blocking requests
1.2 s33 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.0 s
A phone's processor spends 6.0 s on main-thread work while loading, 3.9 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/Doubleclick Ads, Google Tag Manager and Facebook and others), adding 2.5 MB and 2.1 s of main-thread time.
Google/Doubleclick Ads adds 950 ms
950 msGoogle/Doubleclick Ads costs a phone 950 ms of main-thread work and 1.1 MB 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 Tag Manager adds 466 ms
466 msGoogle Tag Manager costs a phone 466 ms of main-thread work and 488 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
450 ms · 34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
Minify JavaScript
300 ms · 41 KiB41 KiB could be saved by minifying JavaScript.
Reduce unused CSS
300 ms · 27 KiBAbout 27 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.
Improve image delivery
324 KiB7 images could be 324 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1,638 HTML elements
The page has 1,638 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 237 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.
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: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 16.4 s
16.4 sYour largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “master toys logo”.
Time to Interactive: 22.7 s
22.7 sThe page becomes fully interactive after 22.7 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 872 ms
872 msScripts block taps and scrolling for 872 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 104 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user INP: 123 ms
123 msReal visitors wait 123 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.5 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.096
0.096The layout barely moves while loading (CLS 0.096, good is under 0.1).
Images and page weight
Page weight: 3.5 MB in 276 requests
3.5 MBYour homepage downloads 3.5 MB in 276 requests on a phone: scripts 2.4 MB (85), images 558 KiB (52) and other files 319 KiB (96). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Master-Toys.webp 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).
About 1.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 118.4 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
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
22 text elements with low contrast
22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Positive tabindex
5 elements have a tabindex above 0, which scrambles the keyboard order.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (35 elements)
All page content should be contained by landmarks: 35 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 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.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 15 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 (93 characters)
Your title is 93 characters, so Google will cut it off around 60: “Gifts & Dec | Gifts & Decorative Accessories - Gift Industry News, Markets, Trends & Prod…”.
137 internal links, 62 external
The homepage links to 137 pages on giftsanddec.com and 62 external pages.
6 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Gifts & Decorative Accessories is a leading trade publication, providing industry news, market coverage, retail tips an…”.
Canonical URL set
The canonical URL is https://www.giftsanddec.com/.
Structured data in place
Structured data found: BreadcrumbList, WebPage 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.
XML sitemap found
Your XML sitemap is reachable at https://www.giftsanddec.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.giftsanddec.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, which the crawlers above handle.
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,129 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages without a meta description
https://www.giftsanddec.com/events, https://www.giftsanddec.com/photo-galleries, https://www.giftsanddec.com/trends, https://www.giftsanddec.com/professional-announcements, https://www.giftsanddec.com/category/btm-business-connect and https://www.giftsanddec.com/behind-the-deal-submission and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.giftsanddec.com/reader-rankings, whose canonical is https://www.giftsanddec.com/reader-rankings-2026. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.giftsanddec.com/advertising 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 79 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
3 broken images
3 images failed to load on a phone, for example https://www.giftsanddec.com/wp-content/uploads/2022/08/User-Login-Icon-1.png.
76 small tap targets
76 of 102 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 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. 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 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.
About 770 words of copy
The homepage carries about 770 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SUBSCRIBE NOW”.
2 calls to action
The homepage has 2 calls to action, for example “Subscribe” and “Contact Us”.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Microsoft Clarity, Hotjar and Cloudflare Web Analytics.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
48 other companies contacted
Loading the homepage contacts 48 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 giftsanddec.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager | Hotjar | Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 55 issues on giftsanddec.com, including 25 speed issues, 2 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.