51774496.com website review

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

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

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

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

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

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

2 third-party services load with your homepage (Google CDN and slovedc.com), adding 37 KiB and 14 ms of main-thread time.

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

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

5 KiB could be saved by minifying CSS.

4 KiB could be saved by minifying JavaScript.

Your largest element takes 10.2 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 10.3 s. Good is under 3.8 s.

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

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

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

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.

10 images (781 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.

1 image is downloaded at several times the size a phone draws it, for example logo-2.png at 700 px wide, shown at 100 px. Resized copies would save about 157 KiB.

7 images further down the page (399 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 14 characters: “債務救星│二線財務│二線清數”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 4 characters: “二線清數”. 70 to 160 characters is enough to sell the click.

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

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://51774496.com/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 14 pages on 51774496.com and 8 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.

/pages/%E4%BA%8C%E7%B7%9A%E8%B2%A1%E5%8B%99.html, /pages/%E4%BA%8C%E7%B7%9A%E6%B8%85%E6%95%B8.html, /pages/%E4%BA%8C%E7%B7%9A%E8%BD%89%E4%BB%8B%E6%9C%8D%E5%8B%99.html, /pages/%E7%A0%B4%E7%94%A2%E8%AB%AE%E8%A9%A2.html, /pages/%E8%81%AF%E7%B5%A1%E6%88%91%E5%80%91.html and /sitemap use the same meta description. A description written for each page earns more clicks.

/pages/%E4%BA%8C%E7%B7%9A%E8%B2%A1%E5%8B%99.html, /pages/%E4%BA%8C%E7%B7%9A%E6%B8%85%E6%95%B8.html, /pages/%E4%BA%8C%E7%B7%9A%E8%BD%89%E4%BB%8B%E6%9C%8D%E5%8B%99.html, /pages/%E7%A0%B4%E7%94%A2%E8%AB%AE%E8%A9%A2.html, /pages/%E8%81%AF%E7%B5%A1%E6%88%91%E5%80%91.html and /sitemap have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/%E4%BA%8C%E7%B7%9A%E8%B2%A1%E5%8B%99.html, /pages/%E4%BA%8C%E7%B7%9A%E6%B8%85%E6%95%B8.html, /pages/%E4%BA%8C%E7%B7%9A%E8%BD%89%E4%BB%8B%E6%9C%8D%E5%8B%99.html, /pages/%E7%A0%B4%E7%94%A2%E8%AB%AE%E8%A9%A2.html, /pages/%E8%81%AF%E7%B5%A1%E6%88%91%E5%80%91.html and /sitemap 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.

/pages/%E8%81%AF%E7%B5%A1%E6%88%91%E5%80%91.html and /sitemap took over 3 s to send their HTML from our server.

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

3 images failed to load on a phone, for example https://parrothero.com/product_images/uploaded_images/icon-facebook-app.png.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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

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

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

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

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

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

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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

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

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

Opening the homepage sets 2 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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.