Website review, no card needed

mkgny.com logo

mkgny.com website review

Visit site (opens in a new tab)Reviewed 3 November 202627 issues · 79 checks

This review found 27 issues worth fixing on mkgny.com, 12 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of mkgny.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mkgny.com at 0.5 s0.5 s
  2. mkgny.com at 0.9 s0.9 s
  3. mkgny.com at 1.4 s1.4 s
  4. mkgny.com at 1.9 s1.9 s
  5. mkgny.com at 2.3 s2.3 s
  6. mkgny.com at 2.8 s2.8 s
  7. mkgny.com at 3.3 s3.3 s
  8. mkgny.com at 3.7 s3.7 s

Speed

7 to fix54
  • Use efficient cache lifetimes

    16.6 s · 3.4 MB

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

  • Render-blocking requests

    8.6 s

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

  • Reduce unused CSS

    6.5 s · 1.3 MB

    About 1.3 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.5 s faster on a phone.

  • Reduce unused JavaScript

    3.3 s · 877 KiB

    About 877 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.

  • Minify JavaScript

    900 ms · 227 KiB

    227 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 54

    54/100

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

  • Minify CSS

    550 ms · 107 KiB

    107 KiB could be saved by minifying CSS.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Maps and Amazon Web Services and others), adding 751 KiB and 291 ms of main-thread time.

  • Improve image delivery

    200 ms · 17 KiB

    2 images could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

  • 4 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Document request latency

    92 KiB

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

  • Legacy JavaScript

    26 KiB

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

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 83 ms

    83 ms

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

Core Web Vitals

5 to fix65
  • First Contentful Paint: 9.8 s

    9.8 s

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

  • Largest Contentful Paint: 20.2 s

    20.2 s

    Your largest element takes 20.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 22.7 s

    22.7 s

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

  • Speed Index: 11.0 s

    11.0 s

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

  • 1 image without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 138 ms

    138 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.1 MB in 65 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 65 requests on a phone: scripts 1.5 MB (18), stylesheets 1.3 MB (12) and images 914 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (107 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.

  • 6 images below the first screen load straight away

    6 images further down the page (183 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.15 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.15 g of CO₂e: 138.2 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

5 to fixGoogle 7590
  • 14 images without alt text

    14 images have no alt text, which hurts accessibility and image search.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 21 links without text

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

1 checks passed
  • 26 automated accessibility rules passed

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

SEO

2 to fixGoogle 9285
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is short (23 characters)

    Your meta description is only 23 characters: “Medical Knowledge Group”. 70 to 160 characters is enough to sell the click.

  • 5 internal links, 15 external

    The homepage links to 5 pages on mkgny.com and 15 external pages.

6 checks passed
  • Title: 30 characters

    Your title is a healthy 30 characters: “Home - Medical Knowledge Group”.

  • Canonical URL set

    The canonical URL is https://mkgny.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://mkgny.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Text is in the HTML

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

Other pages

3 to fix85
  • 1 page without a meta description

    https://mkgny.com/privacy-policy has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mkgny.com/privacy-policy, whose canonical is https://mkgny.com/privacy-policy-2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://mkgny.com/terms-of-use, https://mkgny.com/impact-statement and https://mkgny.com/code-of-conduct have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 4 pages we checked loaded without an error.

  • 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 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7397
  • 6 distorted images

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

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    22 of 25 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 254 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “CONTACT”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

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

  • 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 mkgny.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on mkgny.com, including 12 speed issues, 2 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