Website review, no card needed
gmobile.mn website review
Visit site (opens in a new tab)Reviewed 19 October 202642 issues · 79 checks
This review found 42 issues worth fixing on gmobile.mn, 18 of them high impact, across 79 checks. The most urgent: render-blocking 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
64DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 3.3 s |
| May 2, 2026 | 3.3 s |
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 130 ms |
| May 2, 2026 | 130 ms |
| May 9, 2026 | 131 ms |
| May 16, 2026 | 129 ms |
| May 23, 2026 | 129 ms |
| May 30, 2026 | 129 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 128 ms |
| Jun 20, 2026 | 126 ms |
| Jun 27, 2026 | 122 ms |
| Jul 4, 2026 | 116 ms |
| Jul 11, 2026 | 115 ms |
| Jul 18, 2026 | 116 ms |
| Jul 25, 2026 | 114 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 111 ms |
| Aug 22, 2026 | 112 ms |
| Aug 29, 2026 | 114 ms |
| Sep 5, 2026 | 119 ms |
| Sep 12, 2026 | 122 ms |
| Sep 19, 2026 | 122 ms |
| Sep 26, 2026 | 120 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 120 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
Speed
Render-blocking requests
2.2 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Use efficient cache lifetimes
7.3 MB17 files are served with short cache lifetimes, so returning visitors download them again (7.3 MB).
Improve image delivery
2.7 MB7 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 63
63/100Your mobile performance score is 63 (desktop: 81). Pages that score under 90 lose visitors before the first paint.
3 third-party services on the page
3 third-party services load with your homepage (Other Google APIs/SDKs, Google Fonts and Google CDN), adding 167 KiB and 72 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 82 ms. During a long task the page ignores taps.
Reduce unused JavaScript
61 KiBAbout 61 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 206 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
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.
Real-user LCP: 4.5 s
4.5 sReal visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.46
0.46For real visitors the layout shifts by 0.46 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.407
0.407The layout shifts by 0.407 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 7.9 s
7.9 sThe page becomes fully interactive after 7.9 s. Good is under 3.8 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (4.3 s).
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 130 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 137 ms
137 msReal visitors wait 137 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 477 ms
477 msReal visitors wait 477 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 16 ms
16 msScripts block the page for only 16 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 7.7 MB in 73 requests
7.7 MBYour homepage downloads 7.7 MB in 73 requests on a phone: images 7.4 MB (26), scripts 272 KiB (19) and fonts 43 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (38 KiB) is 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.
About 2.2 g of CO₂ per visit
2.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.19 g of CO₂e: 263.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
Orphan list items
Some list items are not inside a list.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 checks passed
27 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 27 passed and 6 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://gmobile.mn/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at gmobile.mn/robots.txt, the first file search crawlers ask for.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
5 internal links, 0 external
The homepage links to 5 pages on gmobile.mn and 0 external pages.
1 checks passed
Title: 32 characters
Your title is a healthy 32 characters: “Жимобайл ХХК - Үндэсний оператор”.
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://gmobile.mn/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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Other pages
6 pages share a title
/, https://gmobile.mn/about, https://gmobile.mn/branches, https://gmobile.mn/anket, https://gmobile.mn/coverage and https://gmobile.mn/contact all use the title “Жимобайл ХХК - Үндэсний оператор”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://gmobile.mn/about, https://gmobile.mn/branches, https://gmobile.mn/anket, https://gmobile.mn/coverage and https://gmobile.mn/contact have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://gmobile.mn/about, https://gmobile.mn/branches, https://gmobile.mn/coverage and https://gmobile.mn/contact have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages with very little text
https://gmobile.mn/about, https://gmobile.mn/branches, https://gmobile.mn/anket, https://gmobile.mn/coverage and https://gmobile.mn/contact 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.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 5 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 5 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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 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.
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.
Only about 1 words
The homepage has only about 1 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.
Privacy and tracking
3 cookies set on arrival
3Opening 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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 gmobile.mn, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
Company
- Founded
- 2007
- Headquarters
- Ulaanbaatar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on gmobile.mn, including 12 speed issues, 8 SEO 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.