Website review, no card needed

qubeiot.com logo

qubeiot.com website review

Visit site (opens in a new tab)Reviewed 18 October 202640 issues · 82 checks

This review found 40 issues worth fixing on qubeiot.com, 14 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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 qubeiot.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. qubeiot.com at 0.9 s0.9 s
  2. qubeiot.com at 1.8 s1.8 s
  3. qubeiot.com at 2.7 s2.7 s
  4. qubeiot.com at 3.6 s3.6 s
  5. qubeiot.com at 4.5 s4.5 s
  6. qubeiot.com at 5.5 s5.5 s
  7. qubeiot.com at 6.4 s6.4 s
  8. qubeiot.com at 7.3 s7.3 s

Speed

12 to fix30
  • Reduce unused JavaScript

    4.9 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.9 s faster on a phone.

  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 6.4 s

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

  • Improve image delivery

    150 ms · 5.2 MB

    17 images could be 5.2 MB 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Squarespace, Google Tag Manager and Hotjar and others), adding 12.5 MB and 2.3 s of main-thread time.

  • Squarespace adds 828 ms

    828 ms

    Squarespace costs a phone 828 ms of main-thread work and 11.2 MB 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.

  • Reduce unused CSS

    750 ms · 130 KiB

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

  • Google Tag Manager adds 763 ms

    763 ms

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

  • Legacy JavaScript

    450 ms · 132 KiB

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

  • 20 long tasks on the main thread

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

  • Hotjar adds 256 ms

    256 ms

    Hotjar costs a phone 256 ms of main-thread work and 64 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.

  • Use efficient cache lifetimes

    150 ms · 153 KiB

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

  • Minify JavaScript

    150 ms · 45 KiB

    45 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

  • 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: 53 ms

    53 ms

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

Core Web Vitals

6 to fix39
  • Largest Contentful Paint: 42.7 s

    42.7 s

    Your largest element takes 42.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Request a demo”.

  • Time to Interactive: 51.6 s

    51.6 s

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

  • Speed Index: 14.9 s

    14.9 s

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

  • First Contentful Paint: 6.3 s

    6.3 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • 11 images without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 13.0 MB in 172 requests

    13.0 MB

    Your homepage downloads 13.0 MB in 172 requests on a phone: images 9.9 MB (42), scripts 2.6 MB (75) and fonts 230 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    2.0 MB

    6 images are downloaded at several times the size a phone draws them, for example Group+3726.jpg at 1,976 px wide, shown at 390 px. Resized copies would save about 2.0 MB.

  • 10 images in older formats

    10 images (4.4 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.

  • 10 images below the first screen load straight away

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

  • About 3.7 g of CO₂ per visit

    3.68 g

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

Accessibility

3 to fixGoogle 8795
  • 13 text elements with low contrast

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

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • 2 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

5 to fixGoogle 8583
  • 4 H1 headlines

    There are 4 <h1> headlines (“Continuous emissions monitoring for real world op…”, “Continuous emissions monitoring for real world op…” and “Detect. Analyze. Respond.”). One clear main headline is easier for people and search engines.

  • Meta description is long (168 characters)

    Your meta description is 168 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (LocalBusiness, Organization and WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/60625d868b66720e92e…”.

  • 2 links crawlers can't follow

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 75 internal links, 6 external

    The homepage links to 75 pages on qubeiot.com and 6 external pages.

5 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “Emissions Monitoring Solutions by Qube Technologies”.

  • Canonical URL set

    The canonical URL is https://www.qubeiot.com/.

  • 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://www.qubeiot.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    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.

  • No llms.txt

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

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

Other pages

6 to fix69
  • 1 linked page hidden from search

    https://www.qubeiot.com/products is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages share 3 titles

    https://www.qubeiot.com/industries-energy and https://www.qubeiot.com/industries-1 all use the title “Continuous Emissions Monitoring Solutions for Oil and Gas Operations”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.qubeiot.com/resources and https://www.qubeiot.com/schedule-demo have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://www.qubeiot.com/industries-energy and https://www.qubeiot.com/industries-1 use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.qubeiot.com/industries-1, whose canonical is https://www.qubeiot.com/industries-energy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages without an H1

    https://www.qubeiot.com/industries-energy, https://www.qubeiot.com/industries-waste-management, https://www.qubeiot.com/industries-biogas, https://www.qubeiot.com/industries-utilities, https://www.qubeiot.com/platform and https://www.qubeiot.com/contact-qube and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.qubeiot.com/industries-waste-management, https://www.qubeiot.com/careers, https://www.qubeiot.com/support and https://www.qubeiot.com/contact-qube have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.qubeiot.com/styles.css' because its MIME type ('text/html') is not a supported…”.

2 checks passed
  • Tap targets are thumb-sized

    6 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,017 words of copy

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

6 checks passed
  • Clear next step on the first screen

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

  • 17 calls to action

    The homepage has 17 calls to action, for example “Contact Qube”, “Contact | Demo” and “Request a demo”.

  • Analytics in place

    Analytics detected: Google Analytics, Hotjar, HubSpot and LinkedIn Insight.

  • Direct contact links

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

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

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

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

  • 44 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 qubeiot.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
Squarespace
Framework
jQuery
Analytics
Google Analytics | Hotjar

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on qubeiot.com, including 18 speed issues, 5 SEO issues and 1 conversion gap. 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