Website review, no card needed

raytheongod.com logo

raytheongod.com website review

Visit site (opens in a new tab)Reviewed 16 November 202632 issues · 80 checks

This review found 32 issues worth fixing on raytheongod.com, 9 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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 raytheongod.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. raytheongod.com at 0.4 s0.4 s
  2. raytheongod.com at 0.8 s0.8 s
  3. raytheongod.com at 1.3 s1.3 s
  4. raytheongod.com at 1.7 s1.7 s
  5. raytheongod.com at 2.1 s2.1 s
  6. raytheongod.com at 2.5 s2.5 s
  7. raytheongod.com at 2.9 s2.9 s
  8. raytheongod.com at 3.3 s3.3 s

Speed

4 to fix92
  • Use efficient cache lifetimes

    1.6 s · 406 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Improve image delivery

    1.3 s · 197 KiB

    2 images could be 197 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.

  • Font display

    700 ms

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

  • Reduce unused CSS

    160 ms · 19 KiB

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

  • Minify JavaScript

    160 ms · 3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Minify CSS

    160 ms · 2 KiB

    2 KiB could be saved by minifying CSS.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, cnzz.com and Google Analytics), adding 291 KiB and 126 ms of main-thread time.

  • Reduce unused JavaScript

    141 KiB

    About 141 KiB of JavaScript is downloaded but never used on this page.

  • 1 long task on the main thread

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

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

3 checks passed
  • Mobile performance score: 92

    92/100

    Your mobile performance score is 92. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix92
  • Speed Index: 4.2 s

    4.2 s

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

  • Time to Interactive: 4.4 s

    4.4 s

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

  • Cumulative Layout Shift: 0.113

    0.113

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

  • 2 images without width and height

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

3 checks passed
  • Largest Contentful Paint: 2.5 s

    2.5 s

    Your largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “banner”.

  • First Contentful Paint: 1.3 s

    1.3 s

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

  • Total Blocking Time: 16 ms

    16 ms

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

Images and page weight

1 to fix90
  • 1 image far larger than shown

    144 KiB

    1 image is downloaded at several times the size a phone draws it, for example 1772762634385.jpg at 1,903 px wide, shown at 360 px. Resized copies would save about 144 KiB.

  • 1 image in older formats

    1 image (212 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.

  • About 0.2 g of CO₂ per visit

    0.20 g

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

2 checks passed
  • Page weight: 705 KiB in 32 requests

    705 KiB

    Your homepage downloads 705 KiB in 32 requests on a phone: scripts 349 KiB (11), images 238 KiB (12) and fonts 70 KiB (1). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

10 to fixGoogle 5381
  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

  • 11 text elements with low contrast

    11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

  • All page content should be contained by landmarks (13 elements)

    All page content should be contained by landmarks: 13 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 24 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 24 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9282
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 2 links crawlers can't follow

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

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 56 internal links, 1 external

    The homepage links to 56 pages on raytheongod.com and 1 external page.

4 checks passed
  • Meta description: 97 characters

    Your meta description is 97 characters: “为大家整理了全球著名的大电商类SaaS平台Shopify开店和建站教程,shopify引流营销及收款、支付、物流、使用shopify快速开facebook店铺等教程,助您更快掌握shopify。”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “提供实操的shopify开店和建站教程,及跨境电商行业资讯,助您更快掌握shopify”.

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

AI search readiness

1 to fix83
  • 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.raytheongod.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.

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

Other pages

1 to fix95
  • 12 pages without an H1

    https://www.raytheongod.com/xingyedongtai_nc6, https://www.raytheongod.com/zhifufangshi_nc1, https://www.raytheongod.com/paypal_nc10, https://www.raytheongod.com/shoudongzhifufangshi_nc19, https://www.raytheongod.com/shopify-payments_nc9 and https://www.raytheongod.com/shopifyxinshoukaidian_nc2 and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.raytheongod.com/shoudongzhifufangshi_nc19 and https://www.raytheongod.com/yingxiaohecuxiao_nc3 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.

  • 9 pages slow to respond

    https://www.raytheongod.com/zhifufangshi_nc1, https://www.raytheongod.com/paypal_nc10, https://www.raytheongod.com/shoudongzhifufangshi_nc19, https://www.raytheongod.com/shopify-payments_nc9, https://www.raytheongod.com/shopifyxinshoukaidian_nc2 and https://www.raytheongod.com/yingxiaohecuxiao_nc3 and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 12 pages that loaded have a meta description.

  • 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 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 7 small tap targets

    7 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 56 words

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

3 checks passed
  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 2 cookies set on arrival

    2

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 raytheongod.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
E-commerce
Shopify;Shopify Plus
Analytics
Google Analytics
Hosting
Tencent Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on raytheongod.com, including 8 speed issues, 5 SEO issues and 4 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