Website review, no card needed

maxsourceworld.com logo

maxsourceworld.com website review

Visit site (opens in a new tab)Reviewed 21 October 202651 issues · 87 checks

This review found 51 issues worth fixing on maxsourceworld.com, 22 of them high impact, across 87 checks. The most urgent: page weight: 44.9 MB in 200 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
4.8 s2.3 sMay 2Oct 173.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.5 s
May 9, 20264.4 s
May 16, 20264.4 s
May 23, 20264.3 s
May 30, 20264.0 s
Jun 6, 20263.6 s
Jun 13, 20263.0 s
Jun 20, 20262.6 s
Jun 27, 20263.2 s
Jul 4, 20263.9 s
Jul 11, 20264.0 s
Jul 18, 20264.4 s
Jul 25, 20264.5 s
Aug 1, 20264.4 s
Aug 8, 20264.5 s
Sep 5, 20263.9 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
276 ms129 msMay 2Oct 17253 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026160 ms
May 9, 2026161 ms
May 16, 2026170 ms
May 23, 2026169 ms
May 30, 2026168 ms
Jun 6, 2026155 ms
Jun 13, 2026146 ms
Jun 20, 2026150 ms
Jun 27, 2026151 ms
Jul 4, 2026149 ms
Jul 11, 2026154 ms
Jul 18, 2026159 ms
Jul 25, 2026161 ms
Aug 1, 2026165 ms
Aug 8, 2026175 ms
Aug 22, 2026183 ms
Sep 5, 2026197 ms
Sep 12, 2026226 ms
Sep 19, 2026255 ms
Sep 26, 2026259 ms
Oct 3, 2026255 ms
Oct 10, 2026257 ms
Oct 17, 2026253 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 maxsourceworld.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. maxsourceworld.com at 1.4 s1.4 s
  2. maxsourceworld.com at 2.7 s2.7 s
  3. maxsourceworld.com at 4.1 s4.1 s
  4. maxsourceworld.com at 5.4 s5.4 s
  5. maxsourceworld.com at 6.8 s6.8 s
  6. maxsourceworld.com at 8.1 s8.1 s
  7. maxsourceworld.com at 9.5 s9.5 s
  8. maxsourceworld.com at 10.9 s10.9 s

Speed

10 to fix
  • Font display

    3.0 s

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

  • Reduce initial server response time

    1.9 s

    Reduce initial server response time. Google estimates savings of 1.9 s on a phone.

  • Document request latency

    1.9 s

    The HTML itself could arrive about 1.9 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Main-thread work: 5.4 s

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

  • 3,376 HTML elements

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

  • Server response: 2.0 s

    2.0 s

    Your server takes 2.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 8 third-party services on the page

    8 third-party services load with your homepage (reddit, Google Tag Manager and Google CDN and others), adding 525 KiB and 1.4 s of main-thread time.

  • reddit adds 501 ms

    501 ms

    reddit costs a phone 501 ms of main-thread work and 35 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 Tag Manager adds 363 ms

    363 ms

    Google Tag Manager costs a phone 363 ms of main-thread work and 1 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 CDN adds 188 ms

    188 ms

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

  • Forced reflow

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

Core Web Vitals

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

  • Real-user LCP: 4.8 s

    4.8 s

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

  • Real-user FCP: 4.7 s

    4.7 s

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

  • Real-user TTFB: 3.1 s

    3.1 s

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

  • Real-user INP: 280 ms

    280 ms

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

  • Real-user CLS: 0.13

    0.13

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

  • Tap response (INP) got 59% slower for real visitors

    +59%

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

  • 55 images without width and height

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

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

    -15%

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

  • Cumulative Layout Shift: 0.074

    0.074

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

Images and page weight

5 to fix18
  • Page weight: 44.9 MB in 200 requests

    44.9 MB

    Your homepage downloads 44.9 MB in 200 requests on a phone: images 29.5 MB (66), fonts 6.8 MB (10) and HTML 5.8 MB (2). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 21.2 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    2.5 MB

    8 images are downloaded at several times the size a phone draws them, for example digital-marketing.svg at 1,456 px wide, shown at 370 px. Resized copies would save about 2.5 MB.

  • 9 images below the first screen load straight away

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

  • 2 images in older formats

    2 images (1.2 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.

  • About 12.7 g of CO₂ per visit

    12.73 g

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

Accessibility

13 to fixGoogle 6482
  • Images must have alternative text (4 elements)

    Images must have alternative text: 4 elements on the page fail this check, rated critical by axe-core.

  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • Hidden but focusable

    10 elements hidden from screen readers can still receive keyboard focus.

  • 8 text elements with low contrast

    8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • ARIA toggle fields must have an accessible name (6 elements)

    ARIA toggle fields must have an accessible name: 6 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (4 elements)

    ARIA input fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

  • [aria-*] attributes do not have valid values

    [aria-*] attributes do not have valid values (1 element).

  • All page content should be contained by landmarks (30 elements)

    All page content should be contained by landmarks: 30 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.

  • 9 form fields without a label

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

  • 2 links without text

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

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 8584
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “AI Automation & Software Development for U.S. Businesses | Maxsource”.

  • 22 links crawlers can't follow

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

  • Structured data has 5 problems

    Structured data found (BreadcrumbList, CreativeWorkSeries, ImageObject and LocalBusiness) but with 5 problems, for example “Organization: sameAs is not an absolute URL ("LinkedIn: https://www.linkedin.com/organization-guest…”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 253 internal links, 51 external

    The homepage links to 253 pages on maxsourceworld.com and 51 external pages.

5 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Maxsource helps U.S. businesses with AI automation, custom software development, dedicated teams, healthcare technology…”.

  • One H1 headline

    Your main headline reads: “AI Automation & Software Development for U.S. Businesses”.

  • Canonical URL set

    The canonical URL is https://www.maxsourceworld.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://www.maxsourceworld.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.maxsourceworld.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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,187 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    https://www.maxsourceworld.com/service/cakephp-development and https://www.maxsourceworld.com/service/hire-joomla-developers-for-best-solutions all use the title “Hire Skilled Remote Teams for Seamless Growth | Maxsource”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.maxsourceworld.com/service/cakephp-development and https://www.maxsourceworld.com/service/hire-joomla-developers-for-best-solutions use the same meta description. A description written for each page earns more clicks.

  • 11 links to non-canonical URLs

    Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://www.maxsourceworld.com/service/codeigniter-development-company, whose canonical is https://www.maxsourceworld.com/codeigniter-development-company. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.maxsourceworld.com/service/cakephp-development and https://www.maxsourceworld.com/service/hire-joomla-developers-for-best-solutions have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 pages slow to respond

    https://www.maxsourceworld.com/web-and-cms-development, https://www.maxsourceworld.com/service/codeigniter-development-company, https://www.maxsourceworld.com/service/cakephp-development, https://www.maxsourceworld.com/service/python-development, https://www.maxsourceworld.com/service/hire-joomla-developers-for-best-solutions and https://www.maxsourceworld.com/service/ruby-on-rails and 6 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 58 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 13 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 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “window.lintrk is not a function”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix80
  • 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: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 8-field form

    Your longest form asks for 8 fields (7 required). Every extra field lowers completion.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 1,385 words of copy

    The homepage carries about 1,385 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

7 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact Us”, “APPLY NOW” and “Talk to Our Team”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 12 phone links and 11 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 2 cookies set on arrival

    2

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 maxsourceworld.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 | 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 51 issues on maxsourceworld.com, including 18 speed issues, 4 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

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