goodrain.com website review

• Google's speed test didn't respond

  Google's speed test didn't respond for this site, so speed and Core Web Vitals are not measured here. Your full playbook measures them.

Not measured in this review.

• 1 image over 500 KB

  case1.svg weighs 1.4 MB. On a phone connection a single image that size takes seconds.

  Elements (1)

• Page weight: 2.7 MB

  2.7 MB

  Your homepage downloads 2.7 MB on a phone, 2.2 MB of it images (83%). Under 2 MB keeps phones on slow connections fast.

• 5 images in older formats

  5 images (718 KiB) are 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.

  Elements (5)

• About 0.8 g of CO₂ per visit

  0.76 g

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

• 6 text elements with low contrast

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

  Elements (3)

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

  Elements (3)

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• Zoom is disabled

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

  Elements (1)

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

  Elements (1)

• 4 links without text

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

  Elements (3)

• Headings skip levels

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

  View sourceElements (1)

• No H1 headline

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

• Title is long (66 characters)

  Your title is 66 characters, so Google will cut it off around 60: “好雨云平台，好雨，让云落地_提供以应用为中心的云计算产品和服务 :: 好雨云平台，好雨，让云落地_提供以应用为中心的云计算产品和服务”.

  View source

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

• No robots.txt

  There is no robots.txt at goodrain.com/robots.txt, the first file search crawlers ask for.

• No X (Twitter) card tag

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

• 15 internal links, 10 external

  The homepage links to 15 pages on goodrain.com and 10 external pages.

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

• 10 pages share a meta description

  /middle-platform, /business, /multicloud, /saas, /position and /poc and 4 others use the same meta description. A description written for each page earns more clicks.

• 9 pages without an H1

  /middle-platform, /business, /multicloud, /saas, /position and /poc and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 8 pages with very little text

  /middle-platform, /business, /multicloud, /saas, /position and /poc and 2 others 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

  /poc and /about-us took over 3 s to send their HTML from our server.

• 10 internal pages checked

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

• No HSTS header

  No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• HTTP/1.1 only

  The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

• No clickjacking protection

  Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

• No X-Content-Type-Options

  X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  goodrain.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  goodrain.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

• No analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

• Only about 21 words

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

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

• No DMARC policy

  goodrain.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

• No SPF record

  goodrain.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Email authentication score: 0/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 3 cookies set on arrival

  3

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