Website review, no card needed

globusinfocom.com logo

globusinfocom.com website review

Visit site (opens in a new tab)Reviewed 26 October 202641 issues · 79 checks

This review found 41 issues worth fixing on globusinfocom.com, 11 of them high impact, across 79 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
3.0 s2.4 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.9 s
May 16, 20262.9 s
May 23, 20263.0 s
May 30, 20262.9 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.7 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20263.0 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.5 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
168 ms125 msMay 9Oct 24143 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026145 ms
May 16, 2026154 ms
May 23, 2026163 ms
May 30, 2026160 ms
Jun 6, 2026156 ms
Jun 13, 2026146 ms
Jun 20, 2026136 ms
Jun 27, 2026140 ms
Jul 4, 2026156 ms
Jul 11, 2026157 ms
Jul 18, 2026157 ms
Jul 25, 2026156 ms
Aug 1, 2026142 ms
Aug 8, 2026144 ms
Aug 15, 2026140 ms
Aug 22, 2026137 ms
Aug 29, 2026132 ms
Sep 5, 2026132 ms
Sep 12, 2026130 ms
Sep 19, 2026137 ms
Sep 26, 2026139 ms
Oct 3, 2026133 ms
Oct 10, 2026133 ms
Oct 17, 2026139 ms
Oct 24, 2026143 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 globusinfocom.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. globusinfocom.com at 3.8 s3.8 s
  2. globusinfocom.com at 7.7 s7.7 s
  3. globusinfocom.com at 11.5 s11.5 s
  4. globusinfocom.com at 15.4 s15.4 s
  5. globusinfocom.com at 19.2 s19.2 s
  6. globusinfocom.com at 23.1 s23.1 s
  7. globusinfocom.com at 26.9 s26.9 s
  8. globusinfocom.com at 30.7 s30.7 s

Speed

6 to fix55
  • Render-blocking requests

    5.1 s

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

  • Improve image delivery

    450 ms · 9.3 MB

    21 images could be 9.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Use efficient cache lifetimes

    450 ms · 8.2 MB

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    490 ms · 59 KiB

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

  • Reduce unused JavaScript

    330 ms · 131 KiB

    About 131 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 330 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, GoDaddy and jQuery CDN and others), adding 259 KiB and 155 ms of main-thread time.

  • Minify CSS

    160 ms · 15 KiB

    15 KiB could be saved by minifying CSS.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 53 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    9 KiB

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

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 203 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

11 to fix0
  • 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.

  • Speed Index: 16.7 s

    16.7 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Cumulative Layout Shift: 0.316

    0.316

    The layout shifts by 0.316 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest Contentful Paint: 4.1 s

    4.1 s

    Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Emerged as a leading Make-in-India EdTech brand we are comm…”. Most of its time is element render delay (3.1 s).

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user CLS: 0.20

    0.20

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • 32 images without width and height

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

  • Time to Interactive: 4.6 s

    4.6 s

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

  • Tap response (INP) held steady for real visitors

    -6%

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

2 checks passed
  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • Total Blocking Time: 3 ms

    3 ms

    Scripts block the page for only 3 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 16.3 MB in 102 requests

    16.3 MB

    Your homepage downloads 16.3 MB in 102 requests on a phone: images 15.8 MB (41), scripts 395 KiB (37) and stylesheets 94 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 17 images over 500 KB

    17 images weigh 14.0 MB together. On a phone connection a single image that size takes seconds.

  • 24 images far larger than shown

    7.2 MB

    24 images are downloaded at several times the size a phone draws them, for example language-lab_1_.png at 2,100 px wide, shown at 624 px. Resized copies would save about 7.2 MB.

  • 10 images in older formats

    10 images (7.6 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.

  • 16 images below the first screen load straight away

    16 images further down the page (7.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.6 g of CO₂ per visit

    4.62 g

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

Accessibility

4 to fixGoogle 9093
  • No main landmark

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

  • 7 links without text

    7 visible links have no text or label, so screen readers cannot say where they go.

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 40 images in the HTML carry an alt attribute.

  • 24 automated accessibility rules passed

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

SEO

7 to fixGoogle 9270
  • Title is short (22 characters)

    Your title is only 22 characters: “Globus Infocom Limited”. 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.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Creating intelligent and coherent technology ecos…” and “Creating intelligent and coherent technology ecos…”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (170 characters)

    Your meta description is 170 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.

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 41 internal links, 4 external

    The homepage links to 41 pages on globusinfocom.com and 4 external pages.

2 checks passed
  • 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.globusinfocom.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://www.globusinfocom.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 (497 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://www.globusinfocom.com/display/ver/led-wall, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 9 pages without a meta description

    https://www.globusinfocom.com/solution/language-lab-solution, https://www.globusinfocom.com/software/lms-shaala, https://www.globusinfocom.com/solution/paperless-conferencing-solution, https://www.globusinfocom.com/solution/smart-classroom-solution, https://www.globusinfocom.com/camera/ptz-camera and https://www.globusinfocom.com/display/smart-tv and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.globusinfocom.com/partner-with-us has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.globusinfocom.com/partner-with-us, https://www.globusinfocom.com/software/lms-shaala and https://www.globusinfocom.com/software/contentshaala have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://www.globusinfocom.com/camera/ptz-camera took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 33 found) and read each the way a search engine does.

4 checks passed
  • 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.

  • 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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    13 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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: 5 trust badges. 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 271 words of copy

    The homepage carries about 271 words of visible text.

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Support Request”, “Submit Request or Mail to” and “Submit Request”.

  • 1 short form

    A short form (6 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and 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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies (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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 globusinfocom.com, 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 © 2025.

Stack

Framework
jQuery
E-commerce
Magento
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on globusinfocom.com, including 17 speed issues, 7 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

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