premise.com website review

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

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

About 168 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

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

5 third-party services load with your homepage (Google Tag Manager, AddToAny and Marketo and others), adding 517 KiB and 159 ms of main-thread time.

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

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

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

5 KiB could be saved by minifying CSS.

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 visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Unlocking Local Insights, Driving Global Impact Harness the…”.

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

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

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

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

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

Your homepage downloads 2.5 MB in 97 requests on a phone: scripts 990 KiB (38), images 957 KiB (18) and fonts 335 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Structured data found (Article, ImageObject, Organization and Person) but with 1 problem, for example “Article: missing datePublished”.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 60 pages on premise.com and 23 external pages.

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

There is no https://premise.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.

/, https://premise.com/es and https://premise.com/pt all use the title “Premise - Data for Every Decision™”. Search engines can't tell which page to show for a search, so each competes with the others.

https://premise.com/es and https://premise.com/pt use the same meta description. A description written for each page earns more clicks.

https://premise.com/blog and https://premise.com/resources have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://premise.com/.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 481 words of visible text.

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

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

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.

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