Website review, no card needed
newsleopard.com website review
Visit site (opens in a new tab)Reviewed 7 November 202637 issues · 82 checks
This review found 37 issues worth fixing on newsleopard.com, 8 of them high impact, across 82 checks. The most urgent: page weight: 6.3 MB in 140 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 123 ms |
| May 30, 2026 | 131 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 110 ms |
| Jun 20, 2026 | 108 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 108 ms |
| Jul 11, 2026 | 109 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 111 ms |
| Aug 29, 2026 | 137 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 133 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 137 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.3 s
2.0 s
2.6 s
3.3 s
4.0 s
4.6 s
5.3 s
Speed
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.0 MB and 1.2 s of main-thread time.
Improve image delivery
1.3 MB34 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
1.3 MB77 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Reduce unused JavaScript
1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 507 ms
507 msGoogle Tag Manager costs a phone 507 ms of main-thread work and 901 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.
Google CDN adds 377 ms
377 msGoogle CDN costs a phone 377 ms of main-thread work and 736 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.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Document request latency
357 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
2,080 HTML elements
The page has 2,080 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
221 KiBAbout 221 KiB of CSS is downloaded but never applied on this page.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 212 ms. During a long task the page ignores taps.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 39 ms
39 msYour server sent the HTML in 39 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 29.8 s
29.8 sThe page becomes fully interactive after 29.8 s. Good is under 3.8 s.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 821 ms
821 msScripts block taps and scrolling for 821 ms in total while the page loads. Good is under 200 ms.
54 images without width and height
54 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 3.5 s
3.5 sYour largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “電子豹 - 用 AI 拉近你與用戶的距離,為彼此創造更多價值”.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 123 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 708 ms
708 msReal visitors wait 708 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.065
0.065The layout barely moves while loading (CLS 0.065, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 140 requests
6.3 MBYour homepage downloads 6.3 MB in 140 requests on a phone: scripts 2.8 MB (28), images 1.9 MB (71) and HTML 563 KiB (2). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
weddings-cover.jpg weighs 531 KiB. On a phone connection a single image that size takes seconds.
10 images in older formats
10 images (1.4 MB) 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.
8 images below the first screen load straight away
8 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
248 KiB2 images are downloaded at several times the size a phone draws them, for example weddings-cover.jpg at 840 px wide, shown at 240 px. Resized copies would save about 248 KiB.
About 1.8 g of CO₂ per visit
1.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.77 g of CO₂e: 212.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Hidden but focusable
12 elements hidden from screen readers can still receive keyboard focus.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 checks passed
Every image has alt text
All 52 images in the HTML carry an alt attribute.
SEO
55 internal links, 29 external
The homepage links to 55 pages on newsleopard.com and 29 external pages.
8 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “電子豹企業級 Email 行銷和 SMS 簡訊寄送平台,協助超過 15,000 家企業用戶,提供電子報行銷自動化、Email 模版設計工具、品牌會員 EDM 行銷、SMS 簡訊及 API 串接等服務。讓行銷人員都能輕鬆使用的自動化會員行銷…”.
One H1 headline
Your main headline reads: “電子豹 - 用 AI 拉近你與用戶的距離,為彼此創造更多價值”.
Title: 32 characters
Your title is a healthy 32 characters: “電子豹|企業首選電子報行銷平台|SMS 簡訊+Email 自動化”.
Canonical URL set
The canonical URL is https://newsleopard.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://newsleopard.com/sitemap-index.xml.
AI search readiness
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
llms.txt published
The site publishes https://newsleopard.com/llms.txt (44 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://newsleopard.com/surenotify is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://newsleopard.com/features/list-validation has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages with very little text
https://newsleopard.com/features, https://newsleopard.com/features/sms-marketing, https://newsleopard.com/features/website-builder, https://newsleopard.com/features/email-campaign-page, https://newsleopard.com/features/drag-and-drop and https://newsleopard.com/features/automation and 7 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 37 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 68 words
The homepage has only about 68 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (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.
16 cookies set on arrival
16Opening the homepage sets 16 cookies, 7 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.
22 other companies contacted
Loading the homepage contacts 22 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 newsleopard.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
- Gatsby
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on newsleopard.com, including 16 speed issues and 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.