Website review, no card needed
asipartner.com website review
Visit site (opens in a new tab)Reviewed 6 November 202636 issues · 88 checks
This review found 36 issues worth fixing on asipartner.com, 15 of them high impact, across 88 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 270 ms |
| May 23, 2026 | 275 ms |
| May 30, 2026 | 268 ms |
| Jun 6, 2026 | 271 ms |
| Jun 13, 2026 | 270 ms |
| Jun 20, 2026 | 256 ms |
| Jun 27, 2026 | 212 ms |
| Jul 4, 2026 | 118 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 118 ms |
| Jul 25, 2026 | 204 ms |
| Aug 1, 2026 | 254 ms |
| Aug 8, 2026 | 254 ms |
| Aug 15, 2026 | 260 ms |
| Aug 22, 2026 | 260 ms |
| Aug 29, 2026 | 254 ms |
| Sep 5, 2026 | 262 ms |
| Sep 12, 2026 | 261 ms |
| Sep 19, 2026 | 260 ms |
| Sep 26, 2026 | 253 ms |
| Oct 3, 2026 | 253 ms |
| Oct 10, 2026 | 254 ms |
| Oct 17, 2026 | 237 ms |
| Oct 24, 2026 | 237 ms |
| Oct 31, 2026 | 216 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.1 s
1.7 s
2.3 s
2.8 s
3.4 s
3.9 s
4.5 s
Speed
Use efficient cache lifetimes
2.4 s · 1.7 MB58 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Reduce initial server response time
2.3 sReduce initial server response time. Google estimates savings of 2.3 s on a phone.
Document request latency
2.3 sThe HTML itself could arrive about 2.3 s sooner: redirects, a slow server response or missing compression delay everything after it.
Render-blocking requests
1.6 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Server response: 2.4 s
2.4 sYour server takes 2.4 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Reduce unused JavaScript
900 ms · 155 KiBAbout 155 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 194 KiBAbout 194 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
150 ms · 472 KiB13 images could be 472 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and Google Fonts), adding 263 KiB and 68 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 64 ms. During a long task the page ignores taps.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 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.
1 checks passed
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 100 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.
Real-user CLS: 0.31
0.31For real visitors the layout shifts by 0.31 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 7.2 s
7.2 sYour largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Intel Partner Alliance. Click to learn more about the Intel…”.
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: 8.6 s
8.6 sThe page becomes fully interactive after 8.6 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 854 ms
854 msReal visitors wait 854 ms for your server to start answering (75th percentile). Good is under 800 ms.
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: 87 ms
87 msReal visitors wait 87 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 270 ms to 216 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.9 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 7 ms
7 msScripts block the page for only 7 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.1 MB in 63 requests
2.1 MBYour homepage downloads 2.1 MB in 63 requests on a phone: images 1.4 MB (38), scripts 279 KiB (13) and fonts 197 KiB (5). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (342 KiB) 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 (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 72.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
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
3 links inside paragraphs rely on colour alone to stand out.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails 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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
41 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: 41 passed and 8 failed. 1 more need a person to judge. 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.
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 set, so this is minor.
201 internal links, 13 external
The homepage links to 201 pages on asipartner.com and 13 external pages.
7 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “ASI is a leading IT distributor offering AI servers, workstations, storage, networking, and technology solutions for re…”.
Title: 36 characters
Your title is a healthy 36 characters: “ASI | Leading Technology Distributor”.
Canonical URL set
The canonical URL is https://www.asipartner.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.asipartner.com/wp-sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.asipartner.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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (995 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://www.asipartner.com/canada all use the title “ASI | Leading Technology Distributor”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages share a meta description
https://www.asipartner.com/solutions/intel-core-ultra-processors, https://www.asipartner.com/solutions/intel-core-ultra-200v and https://www.asipartner.com/solutions/intel-core-ultra-200-mobile use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://www.asipartner.com/canada, https://www.asipartner.com/company/become-a-partner, https://www.asipartner.com/solutions/gaming/asi-gaming-solutions, https://www.asipartner.com/solutions/ai-pc, https://www.asipartner.com/solutions/mini-pcs and https://www.asipartner.com/solutions/gaming/intel-core-ultra-200s-plus and 8 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 120 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
17 small tap targets
17 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 393 words of copy
The homepage carries about 393 words of visible text.
5 checks passed
7 calls to action
The homepage has 7 calls to action, for example “RMA Request”, “Cross Shipment Request” and “Contact Customer Service”.
4 short forms
4 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and HubSpot.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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.
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.
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 asipartner.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
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Level 3 Parent, LLC
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on asipartner.com, including 17 speed issues, 2 SEO issues and 3 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.