Website review, no card needed

mark-technology.com logo

mark-technology.com website review

Visit site (opens in a new tab)Reviewed 9 November 202635 issues · 80 checks

This review found 35 issues worth fixing on mark-technology.com, 14 of them high impact, across 80 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

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

How it loaded on a phone

  1. mark-technology.com at 1.2 s1.2 s
  2. mark-technology.com at 2.4 s2.4 s
  3. mark-technology.com at 3.6 s3.6 s
  4. mark-technology.com at 4.8 s4.8 s
  5. mark-technology.com at 6.0 s6.0 s
  6. mark-technology.com at 7.2 s7.2 s
  7. mark-technology.com at 8.5 s8.5 s
  8. mark-technology.com at 9.7 s9.7 s

Speed

9 to fix61
  • Render-blocking requests

    3.2 s

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

  • Use efficient cache lifetimes

    1.3 s · 527 KiB

    128 files are served with short cache lifetimes, so returning visitors download them again (527 KiB).

  • Font display

    1.3 s

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

  • Reduce unused CSS

    900 ms · 184 KiB

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

  • Mobile performance score: 61

    61/100

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

  • Reduce unused JavaScript

    450 ms · 168 KiB

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

  • Improve image delivery

    200 ms · 386 KiB

    15 images could be 386 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.

  • Main-thread work: 3.2 s

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

  • 1,873 HTML elements

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

  • Minify CSS

    150 ms · 29 KiB

    29 KiB could be saved by minifying CSS.

  • Minify JavaScript

    150 ms · 5 KiB

    5 KiB could be saved by minifying JavaScript.

  • 5 long tasks on the main thread

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Facebook, Cloudflare and Google Fonts), adding 141 KiB and 50 ms of main-thread time.

  • Legacy JavaScript

    10 KiB

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

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

5 to fix69
  • Speed Index: 15.2 s

    15.2 s

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

  • Largest Contentful Paint: 6.1 s

    6.1 s

    Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Awesome Services Our Awesome services to give you success .…”. Most of its time is resource load delay (3.2 s).

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Time to Interactive: 6.1 s

    6.1 s

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

  • 2 images without width and height

    2 images 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: 160 ms

    160 ms

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

  • Cumulative Layout Shift: 0.016

    0.016

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

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 137 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 137 requests on a phone: images 1.2 MB (28), scripts 483 KiB (43) and fonts 364 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (374 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.7 g of CO₂ per visit

    0.67 g

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

7 to fixGoogle 8991
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

  • 5 images without alt text

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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

6 to fixGoogle 6144
  • Page is set to noindex

    The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 186 internal links, 5 external

    The homepage links to 186 pages on mark-technology.com and 5 external pages.

4 checks passed
  • Title: 35 characters

    Your title is a healthy 35 characters: “Mark Technology – IT Solution world”.

  • Canonical URL set

    The canonical URL is https://mark-technology.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://mark-technology.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://mark-technology.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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 (1,206 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 15 linked pages hidden from search

    https://mark-technology.com/about, https://mark-technology.com/iphone-app-development, https://mark-technology.com/ipad-app-development, https://mark-technology.com/android-app-development, https://mark-technology.com/enterprise-mobile-solutions and https://mark-technology.com/react-native-app-development and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 15 pages without a meta description

    https://mark-technology.com/about, https://mark-technology.com/iphone-app-development, https://mark-technology.com/ipad-app-development, https://mark-technology.com/android-app-development, https://mark-technology.com/enterprise-mobile-solutions and https://mark-technology.com/react-native-app-development and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 3 small tap targets

    3 of 5 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

2 to fix81
  • 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 map 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 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 721 words of copy

    The homepage carries about 721 words of visible text.

6 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 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
  • 1 tracker load before any consent

    1

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

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 mark-technology.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
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on mark-technology.com, including 14 speed issues, 6 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