Website review, no card needed

usam.in logo

usam.in website review

Visit site (opens in a new tab)Reviewed 19 November 202642 issues · 91 checks

This review found 42 issues worth fixing on usam.in, 17 of them high impact, across 91 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.2 s3.0 sMay 30Nov 143.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.0 s
Jun 6, 20264.1 s
Jun 13, 20264.1 s
Jun 20, 20263.9 s
Jun 27, 20263.9 s
Jul 4, 20263.8 s
Jul 11, 20263.7 s
Jul 18, 20263.8 s
Jul 25, 20263.7 s
Aug 1, 20263.8 s
Aug 8, 20263.9 s
Aug 15, 20263.8 s
Aug 22, 20263.7 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.3 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.3 s
Oct 10, 20263.6 s
Oct 17, 20263.6 s
Oct 24, 20263.4 s
Oct 31, 20263.5 s
Nov 7, 20263.5 s
Nov 14, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
195 ms159 msMay 30Nov 14184 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026169 ms
Jun 6, 2026167 ms
Jun 13, 2026166 ms
Jun 20, 2026167 ms
Jun 27, 2026166 ms
Jul 4, 2026169 ms
Jul 11, 2026171 ms
Jul 18, 2026178 ms
Jul 25, 2026173 ms
Aug 1, 2026173 ms
Aug 8, 2026172 ms
Aug 15, 2026164 ms
Aug 22, 2026167 ms
Aug 29, 2026163 ms
Sep 5, 2026164 ms
Sep 12, 2026183 ms
Sep 19, 2026177 ms
Sep 26, 2026177 ms
Oct 3, 2026191 ms
Oct 10, 2026165 ms
Oct 17, 2026164 ms
Oct 24, 2026173 ms
Oct 31, 2026179 ms
Nov 7, 2026178 ms
Nov 14, 2026184 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

Full-page screenshot of usam.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. usam.in at 1.6 s1.6 s
  2. usam.in at 3.2 s3.2 s
  3. usam.in at 4.8 s4.8 s
  4. usam.in at 6.4 s6.4 s
  5. usam.in at 8.1 s8.1 s
  6. usam.in at 9.7 s9.7 s
  7. usam.in at 11.3 s11.3 s
  8. usam.in at 12.9 s12.9 s

Speed

12 to fix42
  • Render-blocking requests

    4.5 s

    86 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.5 s.

  • Use efficient cache lifetimes

    2.3 s · 1.8 MB

    130 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).

  • YouTube adds 1.7 s

    1.7 s

    YouTube costs a phone 1.7 s of main-thread work and 4.9 MB 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.

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.0 s

    A phone's processor spends 6.0 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused JavaScript

    300 ms · 3.1 MB

    About 3.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 6.0 MB and 2.3 s of main-thread time.

  • Font display

    650 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).

  • Reduce unused CSS

    300 ms · 180 KiB

    About 180 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 235 ms

    235 ms

    Google Tag Manager costs a phone 235 ms of main-thread work and 361 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.

  • 2,221 HTML elements

    The page has 2,221 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Google CDN adds 87 ms

    87 ms

    Google CDN costs a phone 87 ms of main-thread work and 352 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 145 ms. During a long task the page ignores taps.

  • Improve image delivery

    57 KiB

    2 images could be 57 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 114 ms

    114 ms

    Your server sent the HTML in 114 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • 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 s

    Real visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 3.9 s

    3.9 s

    Real visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.4 s

    2.4 s

    Real visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 20.5 s

    20.5 s

    Visually, the page fills in at 20.5 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 46.2 s

    46.2 s

    The page becomes fully interactive after 46.2 s. Good is under 3.8 s.

  • Largest Contentful Paint: 6.2 s

    6.2 s

    Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “banner-1-1”. Most of its time is resource load delay (5.4 s).

  • First Contentful Paint: 3.6 s

    3.6 s

    The first text or image appears after 3.6 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 771 ms

    771 ms

    Scripts block taps and scrolling for 771 ms in total while the page loads. Good is under 200 ms.

  • 14 images without width and height

    14 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 169 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 187 ms

    187 ms

    Real visitors wait 187 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 13% faster for real visitors

    -13%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 7.8 MB in 221 requests

    7.8 MB

    Your homepage downloads 7.8 MB in 221 requests on a phone: scripts 5.7 MB (81), fonts 823 KiB (14) and stylesheets 494 KiB (65). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    27 KiB

    1 image is downloaded at several times the size a phone draws it, for example logo.jpg at 489 px wide, shown at 120 px. Resized copies would save about 27 KiB.

  • 2 images in older formats

    2 images (99 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 (41 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.22 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.22 g of CO₂e: 266.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

7 to fixGoogle 8992
  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • 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 (22 elements)

    All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 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.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (24 elements)

    ARIA role should be appropriate for the element: 24 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 261 internal links, 9 external

    The homepage links to 261 pages on usam.in and 9 external pages.

8 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “USAM is a leading IT services and solutions provider with over 30+ years of experience providing business solutions wit…”.

  • One H1 headline

    Your main headline reads: “Technology solutions For your Business”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “IT Services And Solutions Provider | USAM Technology Solutions”.

  • Canonical URL set

    The canonical URL is https://usam.in/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and VideoObject.

  • 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://usam.in/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (1 of 6 facts)

    Your Organization JSON-LD is missing url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://usam.in/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 (875 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix76
  • 2 pages share a title

    https://usam.in/solutions and https://usam.in/printing/3d-printers all use the title “IT Software and Hardware Solutions Provider | USAM Technology Solutio…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://usam.in/catalogue-categories/hp-indigo-printers has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://usam.in/solutions and https://usam.in/printing/3d-printers use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example //blog, whose canonical is https://usam.in/blog. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://usam.in/about, https://usam.in/contact, https://usam.in/hp-a4-printer, https://usam.in/hp-a3-printer, https://usam.in/scanners and https://usam.in/printing/3d-printers and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 pages slow to respond

    //blog, //event-news, //careers, https://usam.in/contact, https://usam.in/solutions and https://usam.in/printing and 7 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 73 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.

  • 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

3 to fixGoogle 7785
  • 13 small tap targets

    13 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 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 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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 514 words of copy

    The homepage carries about 514 words of visible text.

6 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”.

  • 4 short forms

    4 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 2 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.

  • 18 other companies contacted

    Loading the homepage contacts 18 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 usam.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2021.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
InMotion Hosting, Inc.

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 usam.in, including 22 speed issues and 1 SEO issue. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25