Website review, no card needed
bg3.wiki website review
Visit site (opens in a new tab)Reviewed 11 October 202629 issues · 77 checks
This review found 29 issues worth fixing on bg3.wiki, 4 of them high impact, across 77 checks. The most urgent: links look like plain text. 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
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 974 ms |
| Apr 25, 2026 | 978 ms |
| May 2, 2026 | 985 ms |
| May 9, 2026 | 988 ms |
| May 16, 2026 | 990 ms |
| May 23, 2026 | 991 ms |
| May 30, 2026 | 983 ms |
| Jun 6, 2026 | 962 ms |
| Jun 13, 2026 | 940 ms |
| Jun 20, 2026 | 917 ms |
| Jun 27, 2026 | 901 ms |
| Jul 4, 2026 | 902 ms |
| Jul 11, 2026 | 907 ms |
| Jul 18, 2026 | 924 ms |
| Jul 25, 2026 | 938 ms |
| Aug 1, 2026 | 952 ms |
| Aug 8, 2026 | 964 ms |
| Aug 15, 2026 | 972 ms |
| Aug 22, 2026 | 978 ms |
| Aug 29, 2026 | 977 ms |
| Sep 5, 2026 | 960 ms |
| Sep 12, 2026 | 937 ms |
| Sep 19, 2026 | 922 ms |
| Sep 26, 2026 | 910 ms |
| Oct 3, 2026 | 909 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 117 ms |
| Apr 25, 2026 | 118 ms |
| May 2, 2026 | 119 ms |
| May 9, 2026 | 120 ms |
| May 16, 2026 | 120 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 119 ms |
| Jun 6, 2026 | 117 ms |
| Jun 13, 2026 | 114 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 110 ms |
| Aug 1, 2026 | 109 ms |
| Aug 8, 2026 | 109 ms |
| Aug 15, 2026 | 109 ms |
| Aug 22, 2026 | 109 ms |
| Aug 29, 2026 | 109 ms |
| Sep 5, 2026 | 109 ms |
| Sep 12, 2026 | 108 ms |
| Sep 19, 2026 | 109 ms |
| Sep 26, 2026 | 110 ms |
| Oct 3, 2026 | 110 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
Improve image delivery
500 ms · 543 KiB35 images could be 543 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Use efficient cache lifetimes
250 ms · 544 KiB86 files are served with short cache lifetimes, so returning visitors download them again (544 KiB).
8 third-party services on the page
8 third-party services load with your homepage (intergient.com, Google/Doubleclick Ads and Amazon Ads and others), adding 1.1 MB and 562 ms of main-thread time.
Reduce unused JavaScript
665 KiBAbout 665 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
550 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
intergient.com adds 248 ms
248 msintergient.com costs a phone 248 ms of main-thread work and 468 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/Doubleclick Ads adds 132 ms
132 msGoogle/Doubleclick Ads costs a phone 132 ms of main-thread work and 307 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.
Legacy JavaScript
59 KiBPolyfills for old browsers add 59 KiB JavaScript that modern phones do not need.
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.
3 checks passed
Mobile performance score: 91
91/100Your mobile performance score is 91 (desktop: 96). That is in Google's “good” band (90 and up).
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 725 ms of it running JavaScript. That is comfortably low.
Server response: 117 ms
117 msYour server sent the HTML in 117 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 13.9 s
13.9 sThe page becomes fully interactive after 13.9 s. Good is under 3.8 s.
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 213 ms
213 msScripts block taps and scrolling for 213 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 117 ms to 110 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-03, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 127 ms
127 msReal visitors wait 127 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.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 688 ms
688 msReal visitors wait 688 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.7 s
1.7 sYour largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Welcome to bg3.wiki! We provide an accessible, detailed, up…”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.4 MB in 179 requests
2.4 MBYour homepage downloads 2.4 MB in 179 requests on a phone: scripts 1.3 MB (42), images 785 KiB (80) and other files 122 KiB (49). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.67 g of CO₂e: 80.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
Links look like plain text
13 links inside paragraphs rely on colour alone to stand out.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
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.
Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption.
Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption. (1 element).
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (20 characters)
Your title is only 20 characters: “Baldur's Gate 3 Wiki”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (website) but with 1 problem, for example “website: mainEntityOfPage is not an absolute URL ("Baldur's Gate 3 Wiki")”.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
464 internal links, 25 external
The homepage links to 464 pages on bg3.wiki and 25 external pages.
6 checks passed
Meta description: 123 characters
Your meta description is 123 characters: “Welcome to Baldur's Gate 3 Wiki! We provide an accessible, detailed, up to date wiki for Baldur's Gate 3 by Larian Stud…”.
One H1 headline
Your main headline reads: “Baldur's Gate 3 Wiki”.
Canonical URL set
The canonical URL is https://bg3.wiki/.
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://bg3.wiki/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,380 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://bg3.wiki/wiki/Patch_notes, https://bg3.wiki/wiki/bg3wiki:Ads, https://bg3.wiki/wiki/Non-player_characters, https://bg3.wiki/wiki/Items and https://bg3.wiki/wiki/Achievements have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://bg3.wiki/wiki/Help:Getting_started, whose canonical is https://bg3.wiki/wiki/Help:Editing_manual. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 103 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
102 small tap targets
102 of 113 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
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 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
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 740 words of copy
The homepage carries about 740 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Join our Discord” and “join our Discord”.
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Ads (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.
2 other companies contacted
Loading the homepage contacts 2 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 bg3.wiki, 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 29 issues on bg3.wiki, including 10 speed issues, 3 SEO issues and 4 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.