Website review, no card needed

gyewofie.com logo

gyewofie.com website review

Visit site (opens in a new tab)Reviewed 11 November 202620 issues · 66 checks

This review found 20 issues worth fixing on gyewofie.com, 9 of them high impact, across 66 checks. The most urgent: improve image delivery. 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

Full-page screenshot of gyewofie.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gyewofie.com at 0.4 s0.4 s
  2. gyewofie.com at 0.8 s0.8 s
  3. gyewofie.com at 1.1 s1.1 s
  4. gyewofie.com at 1.5 s1.5 s
  5. gyewofie.com at 1.9 s1.9 s
  6. gyewofie.com at 2.3 s2.3 s
  7. gyewofie.com at 2.6 s2.6 s
  8. gyewofie.com at 3.0 s3.0 s

Speed

5 to fix68
  • Improve image delivery

    1.3 s · 407 KiB

    11 images could be 407 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

  • Reduce unused JavaScript

    1.4 s · 243 KiB

    About 243 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    700 ms

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

  • Google Tag Manager adds 110 ms

    110 ms

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Klaviyo and jQuery CDN and others), adding 621 KiB and 180 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 56 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    19 KiB

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

  • Reduce unused CSS

    10 KiB

    About 10 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    7 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (7 KiB).

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

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 309 ms of it running JavaScript. That is comfortably low.

  • Server response: 8 ms

    8 ms

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

Core Web Vitals

3 to fix67
  • Largest Contentful Paint: 9.5 s

    9.5 s

    Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WE'll be back soon”.

  • Time to Interactive: 9.6 s

    9.6 s

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

  • Speed Index: 6.8 s

    6.8 s

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

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

3 checks passed
  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 6 ms

    6 ms

    Scripts block the page for only 6 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix75
  • Page weight: 2.3 MB in 181 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 181 requests on a phone: other files 777 KiB (93), images 714 KiB (17) and scripts 665 KiB (44). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    263 KiB

    4 images are downloaded at several times the size a phone draws them, for example Vector_1_1900x_1_1900x.webp at 1,900 px wide, shown at 390 px. Resized copies would save about 263 KiB.

  • 1 image in older formats

    1 image (153 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 (153 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.7 g of CO₂ per visit

    0.65 g

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

Accessibility

2 to fix91
  • 8 images without alt text

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

  • 6 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

SEO

1 to fixGoogle 9290
  • No H1 headline

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

  • 26 internal links, 11 external

    The homepage links to 26 pages on gyewofie.com and 11 external pages.

7 checks passed
  • Meta description: 126 characters

    Your meta description is 126 characters: “Tramway Path has given away 8 properties, gaining national publicity around our competitions. Visit our website to lear…”.

  • Title: 38 characters

    Your title is a healthy 38 characters: “Win a House Competition | | GYE WO FIE”.

  • Canonical URL set

    The canonical URL is https://gyewofie.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://gyewofie.com/sitemap.xml.

AI search readiness

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

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

  • llms.txt published

    The site publishes https://gyewofie.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    https://gyewofie.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://gyewofie.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://gyewofie.com/collections/all, https://gyewofie.com/customer_authentication/redirect and https://gyewofie.com/pages/enter-via-sms have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://gyewofie.com/collections/all, https://gyewofie.com/customer_authentication/redirect and https://gyewofie.com/pages/enter-via-sms have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://gyewofie.com/collections/all and https://gyewofie.com/pages/enter-via-sms 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.

  • 5 pages slow to respond

    https://gyewofie.com/collections/all, https://gyewofie.com/customer_authentication/redirect, https://gyewofie.com/pages/faqs, https://gyewofie.com/pages/past-winner and https://gyewofie.com/pages/our-story took over 3 s to send their HTML from our server.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 9 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    10 of 10 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

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

  • Only about 99 words

    The homepage has only about 99 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.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BUY NOW”.

  • 1 call to action

    The homepage has 1 call to action, for example “buy now”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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

    13

    Opening the homepage sets 13 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.

  • 13 other companies contacted

    Loading the homepage contacts 13 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 gyewofie.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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Rivo Loyalty Rewards Referrals

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
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on gyewofie.com, including 8 speed issues, 1 SEO issue 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

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