rolcc.net website review

74 files are served with short cache lifetimes, so returning visitors download them again (3.9 MB).

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

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

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

Your mobile performance score is 58 (desktop: 38). Pages that score under 90 lose visitors before the first paint.

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

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

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 531 KiB and 411 ms of main-thread time.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

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.

Your largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 4.6 MB in 86 requests on a phone: images 3.2 MB (15), scripts 816 KiB (30) and fonts 317 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

Your title is 72 characters, so Google will cut it off around 60: “矽谷生命河靈糧堂 River of Life Christian Church – River of Life Christian Church”.

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

There are 4 <h1> headlines (“生命河靈糧堂 River of Life Christian Church homepage”, “北美加州矽谷生命河靈糧堂 歡迎您 River of Life Christian Church w…” and “線上聚會連結”). One clear main headline is easier for people and search engines.

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

No XML sitemap at https://rolcc.net/sitemap.xml, so Google discovers your pages only by following links.

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

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

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

The homepage links to 104 pages on rolcc.net and 62 external pages.

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.

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.

/rolcc2/rolcc-apps, /rolcc2/english-links, /rolcc2/services, /rolcc2/sunday-media, /rolcc2/media/prayermeeting-recordings and /rolcc2/zones-and-cells and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/rolcc2/english-links has no <h1> headline, so visitors and search engines get no clear main topic.

/rolcc2/rolcc-apps, /rolcc2/english-links, /rolcc2/services, /rolcc2/sunday-media, /rolcc2/zones-and-cells and /rolcc2/zones-and-cells/chinese-zones and 8 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.

/rolcc2/rolcc-apps, /rolcc2/english-links, /rolcc2/services, /rolcc2/sunday-media, /rolcc2/media/prayermeeting-recordings and /rolcc2/zones-and-cells and 6 others took over 3 s to send their HTML from our server.

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

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

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

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The homepage shows no opening hours. If customers visit or call, show when.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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.

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