Website review, no card needed

godsloveovercomes.com logo

godsloveovercomes.com website review

Visit site (opens in a new tab)Reviewed 4 November 202647 issues · 79 checks

This review found 47 issues worth fixing on godsloveovercomes.com, 21 of them high impact, across 79 checks. The most urgent: page weight: 86.3 MB in 588 requests. 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
4.7 s3.1 sMay 16Oct 314.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.4 s
Jun 6, 20263.3 s
Jun 13, 20263.3 s
Jun 20, 20263.3 s
Jun 27, 20263.4 s
Jul 4, 20263.5 s
Jul 11, 20263.6 s
Jul 18, 20263.7 s
Jul 25, 20263.7 s
Aug 1, 20263.9 s
Aug 8, 20264.0 s
Aug 15, 20264.0 s
Aug 22, 20264.1 s
Aug 29, 20264.1 s
Sep 5, 20264.0 s
Sep 12, 20264.0 s
Sep 19, 20263.9 s
Sep 26, 20263.8 s
Oct 3, 20264.0 s
Oct 10, 20264.1 s
Oct 17, 20264.3 s
Oct 24, 20264.4 s
Oct 31, 20264.5 s
Real-visitor tap response (INP)75th percentile, phones
211 ms146 msMay 16Oct 31179 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026179 ms
May 23, 2026178 ms
May 30, 2026179 ms
Jun 6, 2026178 ms
Jun 13, 2026179 ms
Jun 20, 2026187 ms
Jun 27, 2026187 ms
Jul 4, 2026186 ms
Jul 11, 2026180 ms
Jul 18, 2026174 ms
Jul 25, 2026174 ms
Aug 1, 2026186 ms
Aug 8, 2026195 ms
Aug 15, 2026196 ms
Aug 22, 2026203 ms
Aug 29, 2026196 ms
Sep 5, 2026179 ms
Sep 12, 2026170 ms
Sep 19, 2026161 ms
Sep 26, 2026153 ms
Oct 3, 2026161 ms
Oct 10, 2026168 ms
Oct 17, 2026171 ms
Oct 24, 2026179 ms
Oct 31, 2026179 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 godsloveovercomes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. godsloveovercomes.com at 0.8 s0.8 s
  2. godsloveovercomes.com at 1.6 s1.6 s
  3. godsloveovercomes.com at 2.4 s2.4 s
  4. godsloveovercomes.com at 3.2 s3.2 s
  5. godsloveovercomes.com at 4.0 s4.0 s
  6. godsloveovercomes.com at 4.9 s4.9 s
  7. godsloveovercomes.com at 5.7 s5.7 s
  8. godsloveovercomes.com at 6.5 s6.5 s

Speed

12 to fix15
  • Avoid multiple page redirects

    3.8 s

    The page goes through 2 redirects before it starts loading, costing about 3.8 s. Link and advertise the final URL directly.

  • Render-blocking requests

    1.2 s

    20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

  • Mobile performance score: 15

    15/100

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

  • Main-thread work: 6.5 s

    A phone's processor spends 6.5 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused JavaScript

    750 ms · 1,018 KiB

    About 1,018 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Improve image delivery

    1.7 MB

    10 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and Clarity and others), adding 2.0 MB and 1.4 s of main-thread time.

  • Use efficient cache lifetimes

    1,015 KiB

    44 files are served with short cache lifetimes, so returning visitors download them again (1,015 KiB).

  • Google Tag Manager adds 732 ms

    732 ms

    Google Tag Manager costs a phone 732 ms of main-thread work and 1.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.

  • 17 long tasks on the main thread

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

  • alia-prod.com adds 300 ms

    300 ms

    alia-prod.com costs a phone 300 ms of main-thread work and 281 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.

  • 2,698 HTML elements

    The page has 2,698 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused CSS

    150 ms · 21 KiB

    About 21 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Document request latency

    100 ms

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

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

  • 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: 34 ms

    34 ms

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

Core Web Vitals

11 to fix33
  • 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 CLS: 0.73

    0.73

    For real visitors the layout shifts by 0.73 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 34.5 s

    34.5 s

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

  • Speed Index: 24.3 s

    24.3 s

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

  • Time to Interactive: 58.3 s

    58.3 s

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

  • First Contentful Paint: 5.8 s

    5.8 s

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

  • Cumulative Layout Shift: 0.781

    0.781

    The layout shifts by 0.781 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 678 ms

    678 ms

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Largest content (LCP) got 28% slower for real visitors

    +28%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 179 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user TTFB: 525 ms

    525 ms

    Real visitors wait 525 ms for your server to start answering (75th percentile). Good is under 800 ms.

Images and page weight

1 to fix33
  • Page weight: 86.3 MB in 588 requests

    86.3 MB

    Your homepage downloads 86.3 MB in 588 requests on a phone: media 71.6 MB (10), images 9.0 MB (68) and scripts 3.2 MB (204). Under 2 MB keeps phones on slow connections fast.

  • About 24.4 g of CO₂ per visit

    24.45 g

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

Accessibility

6 to fixGoogle 8883
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • 17 images without alt text

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

  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

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

  • 2 tap targets too small

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 20 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 7766
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (3 characters)

    Your title is only 3 characters: “GLO”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 20 links crawlers can't follow

    20 links have no real href, so search engines can't follow them.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 46 internal links, 0 external

    The homepage links to 46 pages on godsloveovercomes.com and 0 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.godsloveovercomes.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.godsloveovercomes.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.godsloveovercomes.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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

Other pages

4 to fix58
  • 1 linked page is broken

    Your homepage links to https://www.godsloveovercomes.com/collections/glo-kingdom-essential, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    / and https://www.godsloveovercomes.com/apps/wishlist all use the title “GLO”. 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://www.godsloveovercomes.com/collections/best-sellers-2, https://www.godsloveovercomes.com/collections/new-arrivals-2026, https://www.godsloveovercomes.com/collections/ke-hoodies-collection, https://www.godsloveovercomes.com/collections/crewneck-sweatshirts-1, https://www.godsloveovercomes.com/collections/ke-bottoms-collections and https://www.godsloveovercomes.com/collections/ke-t-shirt-collection and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.godsloveovercomes.com/collections/best-sellers-2, https://www.godsloveovercomes.com/collections/new-arrivals-2026, https://www.godsloveovercomes.com/collections/ke-hoodies-collection, https://www.godsloveovercomes.com/collections/crewneck-sweatshirts-1, https://www.godsloveovercomes.com/collections/ke-bottoms-collections and https://www.godsloveovercomes.com/collections/ke-t-shirt-collection and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://www.godsloveovercomes.com/collections/best-sellers-2, https://www.godsloveovercomes.com/collections/crewneck-sweatshirts-1, https://www.godsloveovercomes.com/collections/ke-t-shirt-collection, https://www.godsloveovercomes.com/collections/accessories, https://www.godsloveovercomes.com/pages/ambassador-page and https://www.godsloveovercomes.com/pages/about-us and 1 other 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.

  • 2 pages slow to respond

    https://www.godsloveovercomes.com/collections/new-arrivals-2026 and https://www.godsloveovercomes.com/collections/ke-hoodies-collection took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • A 10-field form

    Your longest form asks for 10 fields (3 required). Every extra field lowers completion.

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

  • Only about 10 words

    The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 15 calls to action

    The homepage has 15 calls to action, for example “Shop Now”, “SHOP NOW” and “SHOP”.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

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

  • 2 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 godsloveovercomes.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on godsloveovercomes.com, including 23 speed issues, 7 SEO issues and 5 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

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