Website review, no card needed
linkqage.com website review
Visit site (opens in a new tab)Reviewed 3 November 202612 issues · 41 checks
This review found 12 issues worth fixing on linkqage.com, 7 of them high impact, across 41 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 16.0 s |
| May 23, 2026 | 16.6 s |
| May 30, 2026 | 17.5 s |
| Jun 6, 2026 | 17.8 s |
| Jun 13, 2026 | 18.1 s |
| Jun 20, 2026 | 18.4 s |
| Jun 27, 2026 | 18.5 s |
| Jul 4, 2026 | 18.6 s |
| Jul 11, 2026 | 18.9 s |
| Jul 18, 2026 | 19.0 s |
| Jul 25, 2026 | 19.4 s |
| Aug 1, 2026 | 19.9 s |
| Aug 8, 2026 | 19.8 s |
| Aug 15, 2026 | 19.8 s |
| Aug 22, 2026 | 19.7 s |
| Aug 29, 2026 | 19.1 s |
| Sep 5, 2026 | 18.8 s |
| Sep 12, 2026 | 18.1 s |
| Sep 19, 2026 | 17.5 s |
| Sep 26, 2026 | 17.2 s |
| Oct 3, 2026 | 17.2 s |
| Oct 10, 2026 | 17.2 s |
| Oct 17, 2026 | 17.2 s |
| Oct 24, 2026 | 17.4 s |
| Oct 31, 2026 | 17.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 164 ms |
| May 23, 2026 | 173 ms |
| May 30, 2026 | 175 ms |
| Jun 6, 2026 | 177 ms |
| Jun 13, 2026 | 173 ms |
| Jun 20, 2026 | 171 ms |
| Jun 27, 2026 | 165 ms |
| Jul 4, 2026 | 160 ms |
| Jul 11, 2026 | 160 ms |
| Jul 18, 2026 | 160 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 173 ms |
| Aug 8, 2026 | 181 ms |
| Aug 15, 2026 | 184 ms |
| Aug 22, 2026 | 183 ms |
| Aug 29, 2026 | 189 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 194 ms |
| Sep 19, 2026 | 189 ms |
| Sep 26, 2026 | 181 ms |
| Oct 3, 2026 | 174 ms |
| Oct 10, 2026 | 166 ms |
| Oct 17, 2026 | 171 ms |
| Oct 24, 2026 | 166 ms |
| Oct 31, 2026 | 167 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
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 17.5 s
17.5 sReal visitors wait 17.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 15.8 s
15.8 sReal visitors see the first content after 15.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 9.1 s
9.1 sReal visitors wait 9.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 164 ms to 167 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 16.0 s to 17.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 167 ms
167 msReal visitors wait 167 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Images and page weight
About 0.07 g of CO₂ per visit
0.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.07 g of CO₂e: 7.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 237 KiB
237 KiBYour homepage downloads 237 KiB on a phone. That is a lean page.
Accessibility
12 images without alt text
12 images have no alt text, which hurts accessibility and image search.
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.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
3 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 5 WCAG 2.2 A/AA and best-practice rules on the phone render: 3 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (15 characters)
Your title is only 15 characters: “Home - Linkqage”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (214 characters)
Your meta description is 214 characters; Google truncates after about 160, so the end of your pitch is cut.
542 internal links, 5 external
The homepage links to 542 pages on linkqage.com and 5 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.linkqage.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage 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://www.linkqage.com/sitemap_index.xml.
AI search readiness
2 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
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.
Thin social proof
Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 1,640 words of copy
The homepage carries about 1,640 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Login / Register”, “Contact” and “CONTACT”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
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.
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 linkqage.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 12 issues on linkqage.com, including 4 speed issues, 3 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.