Website review, no card needed
ginissima.com website review
Visit site (opens in a new tab)Reviewed 10 November 202638 issues · 80 checks
This review found 38 issues worth fixing on ginissima.com, 9 of them high impact, across 80 checks. The most urgent: render-blocking requests. 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
87B- #7,648 of 109,350 reviewed websitesbeats 90%
- #4,460 of 61,859 online storesbeats 89%
- #4,330 of 56,401 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.3 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 86
86/100Your mobile performance score is 86. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Klarna, Shopify and addons.business and others), adding 6.5 MB and 259 ms of main-thread time.
Shopify adds 80 ms
80 msShopify costs a phone 80 ms of main-thread work and 6.2 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.
Improve image delivery
318 KiB14 images could be 318 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 761 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,018 HTML elements
The page has 2,018 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
190 KiBAbout 190 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
100 ms · 33 KiB7 files are served with short cache lifetimes, so returning visitors download them again (33 KiB).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 91 ms. During a long task the page ignores taps.
Legacy JavaScript
49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need.
Reduce unused CSS
40 KiBAbout 40 KiB of CSS is downloaded but never applied on this page.
Duplicated JavaScript
13 KiB13 KiB JavaScript is shipped twice across bundles.
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: 51 ms
51 msYour server sent the HTML in 51 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 8.2 s
8.2 sThe page becomes fully interactive after 8.2 s. Good is under 3.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Discover the comfort of Ginissima”. Most of its time is element render delay (2.5 s).
1 image without width and height
1 image 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.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 40 ms
40 msScripts block the page for only 40 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.0 MB in 226 requests
8.0 MBYour homepage downloads 8.0 MB in 226 requests on a phone: media 5.4 MB (1), other files 907 KiB (103) and images 850 KiB (43). Under 2 MB keeps phones on slow connections fast.
About 2.3 g of CO₂ per visit
2.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.26 g of CO₂e: 271.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
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.
16 form fields without a label
16 form fields have no label, so screen readers announce an empty box and autofill guesses.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 58 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (15 characters)
Your title is only 15 characters: “Ginissima Shoes”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (284 characters)
Your meta description is 284 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
67 internal links, 21 external
The homepage links to 67 pages on ginissima.com and 21 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://ginissima.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://ginissima.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (836 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ginissima.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://ginissima.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://ginissima.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
7 pages without a meta description
https://ginissima.com/pages/wishlist, https://ginissima.com/collections/new-in, https://ginissima.com/collections/high-heels, https://ginissima.com/collections/low-heels, https://ginissima.com/collections/boots and https://ginissima.com/collections/bridal and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://ginissima.com/products/milla-grey-leather-boots-under-knee, https://ginissima.com/products/milla-brown-leather-boots-under-knee and https://ginissima.com/products/milla-black-leather-boots-under-knee use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://ginissima.com/customer_authentication/redirect 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 23 found) and read each the way a search engine does.
3 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.
Best practices
18 small tap targets
18 of 68 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 12 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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 429 words of copy
The homepage carries about 429 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now”.
5 calls to action
The homepage has 5 calls to action, for example “Register”, “Shop now” and “Shop collection”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
12 other companies contacted
Loading the homepage contacts 12 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 ginissima.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Foxkit Upsell Bundles · Judge Me Reviews · Cozy Country Redirect · Hulk Product Options · Klarna On Site Messaging · addons.business · amazonaws.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
- Framework
- Tailwind CSS
- 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 38 issues on ginissima.com, including 12 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.