Website review, no card needed
netcoreunbxd.com website review
Visit site (opens in a new tab)Reviewed 1 November 202643 issues · 80 checks
This review found 43 issues worth fixing on netcoreunbxd.com, 17 of them high impact, across 80 checks. The most urgent: 2 images over 500 KB. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.6 s |
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 147 ms |
| May 16, 2026 | 154 ms |
| May 30, 2026 | 155 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 157 ms |
| Jun 20, 2026 | 160 ms |
| Jun 27, 2026 | 160 ms |
| Jul 4, 2026 | 160 ms |
| Jul 11, 2026 | 173 ms |
| Jul 18, 2026 | 174 ms |
| Jul 25, 2026 | 173 ms |
| Aug 1, 2026 | 172 ms |
| Aug 8, 2026 | 194 ms |
| Aug 15, 2026 | 194 ms |
| Aug 22, 2026 | 215 ms |
| Aug 29, 2026 | 216 ms |
| Sep 5, 2026 | 211 ms |
| Sep 12, 2026 | 181 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 155 ms |
| Oct 17, 2026 | 163 ms |
| Oct 24, 2026 | 171 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.6 s
1.2 s
1.9 s
2.5 s
3.1 s
3.7 s
4.4 s
5.0 s
Speed
Google Tag Manager adds 1.5 s
1.5 sGoogle Tag Manager costs a phone 1.5 s of main-thread work and 854 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 4.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
4.6 MBAbout 4.6 MB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Hotjar and Facebook and others), adding 1.3 MB and 2.5 s of main-thread time.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 470 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
386 KiB22 files are served with short cache lifetimes, so returning visitors download them again (386 KiB).
Hotjar adds 324 ms
324 msHotjar costs a phone 324 ms of main-thread work and 65 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.
Improve image delivery
166 KiB9 images could be 166 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
Reduce unused CSS
18 KiBAbout 18 KiB of CSS is downloaded but never applied on this page.
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.
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: 13 ms
13 msYour server sent the HTML in 13 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.
Time to Interactive: 42.3 s
42.3 sThe page becomes fully interactive after 42.3 s. Good is under 3.8 s.
Total Blocking Time: 2.8 s
2.8 sScripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.
Speed Index: 11.2 s
11.2 sVisually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 147 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 184 ms
184 msReal visitors wait 184 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 30% faster for real visitors
-30%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.6 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.046
0.046The layout barely moves while loading (CLS 0.046, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.1 s
1.1 sYour largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “For the third consecutive year, Netcore Unbxd has been name…”.
Images and page weight
2 images over 500 KB
2 images weigh 21.1 MB together. On a phone connection a single image that size takes seconds.
Page weight: 7.3 MB in 190 requests
7.3 MBYour homepage downloads 7.3 MB in 190 requests on a phone: scripts 5.8 MB (55), images 1.3 MB (52) and other files 85 KiB (79). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
4.5 MB2 images are downloaded at several times the size a phone draws them, for example hero_gif.gif at 1,024 px wide, shown at 310 px. Resized copies would save about 4.5 MB.
2 images in older formats
2 images (21.1 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.
1 image below the first screen load straight away
1 image further down the page (1.0 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.08 g of CO₂e: 249.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
Interactive controls must not be nested (4 elements)
Interactive controls must not be nested: 4 elements on the page fail this check, rated serious 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.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 7 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (5 characters)
Your title is only 5 characters: “UNBXD”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
6 H1 headlines
There are 6 <h1> headlines (“40%”, “35%” and “80%”). One clear main headline is easier for people and search engines.
Meta description is long (163 characters)
Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
89 internal links, 15 external
The homepage links to 89 pages on netcoreunbxd.com and 15 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://netcoreunbxd.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://netcoreunbxd.com/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://netcoreunbxd.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.
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,043 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages without a title
https://netcoreunbxd.com/demo, https://netcoreunbxd.com/solutions/electronics, https://netcoreunbxd.com/solutions/fashion, https://netcoreunbxd.com/solutions/furniture, https://netcoreunbxd.com/solutions/mid-market and https://netcoreunbxd.com/solutions/jewelry and 4 others have no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://netcoreunbxd.com/integrations/search-shopify is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
10 pages without a meta description
https://netcoreunbxd.com/demo, https://netcoreunbxd.com/solutions/electronics, https://netcoreunbxd.com/solutions/fashion, https://netcoreunbxd.com/solutions/furniture, https://netcoreunbxd.com/solutions/mid-market and https://netcoreunbxd.com/solutions/jewelry and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://netcoreunbxd.com/recommendations/merchandising, https://netcoreunbxd.com/recommendations/algorithms, https://netcoreunbxd.com/recommendations/reports-and-insights, https://netcoreunbxd.com/solutions/electronics, https://netcoreunbxd.com/solutions/fashion and https://netcoreunbxd.com/solutions/furniture and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
3 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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://id.rlcdn.com/464526.gif.
56 small tap targets
56 of 75 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 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.
About 832 words of copy
The homepage carries about 832 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
3 calls to action
The homepage has 3 calls to action, for example “Contact Us” and “LEARN MORE”.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 2 mores (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.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 3 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.
42 other companies contacted
Loading the homepage contacts 42 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 netcoreunbxd.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 Tag Manager
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on netcoreunbxd.com, including 15 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.