Website review, no card needed
cgcorpglobal.com website review
Visit site (opens in a new tab)Reviewed 29 October 202641 issues · 79 checks
This review found 41 issues worth fixing on cgcorpglobal.com, 16 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 113 ms |
| May 16, 2026 | 113 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 115 ms |
| Jun 6, 2026 | 108 ms |
| Jun 13, 2026 | 110 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 109 ms |
| Jul 11, 2026 | 106 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 98 ms |
| Aug 8, 2026 | 97 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 99 ms |
| Sep 12, 2026 | 100 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 97 ms |
| Oct 3, 2026 | 99 ms |
| Oct 10, 2026 | 100 ms |
| Oct 17, 2026 | 99 ms |
| Oct 24, 2026 | 99 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
1.1 s
2.2 s
3.3 s
4.3 s
5.4 s
6.5 s
7.6 s
8.7 s
Speed
Use efficient cache lifetimes
4.3 s · 7.1 MB38 files are served with short cache lifetimes, so returning visitors download them again (7.1 MB).
Render-blocking requests
5.0 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.
Reduce unused JavaScript
3.1 s · 460 KiBAbout 460 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Font display
2.9 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.9 s).
Reduce unused CSS
1.9 s · 461 KiBAbout 461 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
700 ms · 5.1 MB18 images could be 5.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
Document request latency
500 ms · 67 KiBThe HTML itself could arrive about 500 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
523 msReduce initial server response time. Google estimates savings of 523 ms on a phone.
Legacy JavaScript
500 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.
Vimeo adds 35 ms
35 msVimeo costs a phone 35 ms of main-thread work and 611 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.
Server response: 623 ms
623 msYour server takes 623 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Vimeo and Google Analytics), adding 775 KiB and 147 ms of main-thread time.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 97 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.
1 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 536 ms of it running JavaScript. That is comfortably low.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 15.1 s
15.1 sYour largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 13.9 s
13.9 sVisually, the page fills in at 13.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 22.6 s
22.6 sThe page becomes fully interactive after 22.6 s. Good is under 3.8 s.
First Contentful Paint: 6.8 s
6.8 sThe first text or image appears after 6.8 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.32
0.32The layout shifts by 0.32 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 99 ms
99 msReal visitors wait 99 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 113 ms to 99 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 77 ms
77 msScripts block the page for only 77 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 7.9 MB in 54 requests
7.9 MBYour homepage downloads 7.9 MB in 54 requests on a phone: images 6.4 MB (24), scripts 854 KiB (9) and stylesheets 492 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 2.2 g of CO₂ per visit
2.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.24 g of CO₂e: 268.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
No main landmark
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)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 55 images in the HTML carry an alt attribute.
5 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 5 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “CG Corp Global – A multinational corporate operating out of Nepal since 1935”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
85 internal links, 12 external
The homepage links to 85 pages on cgcorpglobal.com and 12 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Foundation”.
Canonical URL set
The canonical URL is https://cgcorpglobal.com/.
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://cgcorpglobal.com/wp-sitemap.xml.
AI search readiness
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://cgcorpglobal.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 linked page is broken
Your homepage links to https://cgcorpglobal.com/companies/hydropwer, which answers with an error. Visitors hit a dead end and search engines drop it.
13 pages without a meta description
https://cgcorpglobal.com/our-story/about, https://cgcorpglobal.com/our-story/milestone, https://cgcorpglobal.com/our-story/binod-chaudhary, https://cgcorpglobal.com/our-story/leadership, https://cgcorpglobal.com/companies/cg-foods and https://cgcorpglobal.com/companies/financial-services and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://cgcorpglobal.com/our-story/about, https://cgcorpglobal.com/our-story/milestone, https://cgcorpglobal.com/our-story/binod-chaudhary, https://cgcorpglobal.com/our-story/leadership, https://cgcorpglobal.com/companies/cg-foods and https://cgcorpglobal.com/companies/mobile and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
12 pages slow to respond
https://cgcorpglobal.com/our-story/about, https://cgcorpglobal.com/our-story/milestone, https://cgcorpglobal.com/our-story/binod-chaudhary, https://cgcorpglobal.com/our-story/leadership, https://cgcorpglobal.com/companies/cg-foods and https://cgcorpglobal.com/companies/financial-services and 6 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 32 found) and read each the way a search engine does.
4 checks passed
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
20 distorted images
20 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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.
About 530 words of copy
The homepage carries about 530 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact” and “Learn More”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 trust badge and “over 202 companies”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
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.
1 other company contacted
Loading the homepage contacts 1 host 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 cgcorpglobal.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Analytics
- Google Analytics
- Hosting
- Akamai Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on cgcorpglobal.com, including 22 speed issues, 5 SEO issues and 2 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.