marklogic.com website review

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

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

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

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

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

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

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

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

1 image could be 115 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 48 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 46 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

2 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Marklogic background”.

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

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

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

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

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

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

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

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

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

1 image is downloaded at several times the size a phone draws it, for example resource-featured-image-770x4334084154184274f1595a6bd484e66f at 1,540 px wide, shown at 350 px. Resized copies would save about 66 KiB.

1 image (123 KiB) is 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.

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

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

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.

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

Your title is 85 characters, so Google will cut it off around 60: “The Most Flexible, AI-Ready Multi-Model Data Management Platform | Progress Marklogic”.

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

Structured data found (BreadcrumbList and Organization) but with 1 problem, for example “Organization: missing name”.

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

The homepage links to 176 pages on marklogic.com and 38 external pages.

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

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'getAttribute')”.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 849 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, LinkedIn Insight, Meta Pixel and Microsoft Ads and 2 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 8 cookies (measured from a US location before any click).

Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.