Website review, no card needed

phenixrts.com logo

phenixrts.com website review

Visit site (opens in a new tab)Reviewed 21 October 202628 issues · 72 checks

This review found 28 issues worth fixing on phenixrts.com, 8 of them high impact, across 72 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 phenixrts.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. phenixrts.com at 0.4 s0.4 s
  2. phenixrts.com at 0.8 s0.8 s
  3. phenixrts.com at 1.1 s1.1 s
  4. phenixrts.com at 1.5 s1.5 s
  5. phenixrts.com at 1.9 s1.9 s
  6. phenixrts.com at 2.3 s2.3 s
  7. phenixrts.com at 2.6 s2.6 s
  8. phenixrts.com at 3.0 s3.0 s

Speed

10 to fix61
  • Use efficient cache lifetimes

    1.1 s · 11.4 MB

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

  • Render-blocking requests

    3.1 s

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

  • Reduce unused JavaScript

    1.1 s · 1.2 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, hsappstatic.net and Hubspot and others), adding 15.1 MB and 1.2 s of main-thread time.

  • website-files.com adds 137 ms

    137 ms

    website-files.com costs a phone 137 ms of main-thread work and 12.0 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.

  • Mobile performance score: 61

    61/100

    Your mobile performance score is 61 (desktop: 71). Pages that score under 90 lose visitors before the first paint.

  • Google CDN adds 448 ms

    448 ms

    Google CDN costs a phone 448 ms of main-thread work and 1.5 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.

  • hsappstatic.net adds 191 ms

    191 ms

    hsappstatic.net costs a phone 191 ms of main-thread work and 813 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.

  • Main-thread work: 2.7 s

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

  • Hubspot adds 165 ms

    165 ms

    Hubspot costs a phone 165 ms of main-thread work and 420 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.

  • 13 long tasks on the main thread

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

  • Improve image delivery

    102 KiB

    5 images could be 102 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    69 KiB

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

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

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix67
  • Time to Interactive: 23.5 s

    23.5 s

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

  • Largest Contentful Paint: 6.2 s

    6.2 s

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

  • First Contentful Paint: 4.5 s

    4.5 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • 18 images without width and height

    18 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: 187 ms

    187 ms

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

  • Cumulative Layout Shift: 0.025

    0.025

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

Images and page weight

1 to fix70
  • Page weight: 15.9 MB in 97 requests

    15.9 MB

    Your homepage downloads 15.9 MB in 97 requests on a phone: media 11.0 MB (2), scripts 2.7 MB (28) and fonts 871 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (30 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.

  • About 4.5 g of CO₂ per visit

    4.52 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9896
  • All page content should be contained by landmarks (17 elements)

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

  • No main landmark

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • No structured data

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

  • No canonical URL

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

  • 4 links with vague text

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

  • 103 internal links, 14 external

    The homepage links to 103 pages on phenixrts.com and 14 external pages.

6 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “As the leading interactive live streaming platform, Phenix is able to deliver video to millions of viewers around the g…”.

  • One H1 headline

    Your main headline reads: “Phenix Delivers Video In Real-Time. In Sync. At Scale.”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Real-Time. In Sync. At Scale. | Phenix Real Time.”.

  • 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.phenixrts.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://www.phenixrts.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 (589 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 4 pages without an H1

    https://www.phenixrts.com/partner-programs, https://www.phenixrts.com/partner-programs/value-added-reseller, https://www.phenixrts.com/partner-programs/technology-partner and https://www.phenixrts.com/partner-programs/cloud-marketplace-program have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 7389
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • No direct contact details

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

  • No form on the homepage

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

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

    The homepage carries about 440 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 12 calls to action

    The homepage has 12 calls to action, for example “Contact Us”, “FREE TRIAL” and “Learn More”.

  • Social proof on the page

    Social proof on the homepage: 32 testimonial or review blocks and 4 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Analytics, HubSpot and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and HubSpot (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.

  • 21 other companies contacted

    Loading the homepage contacts 21 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 phenixrts.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on phenixrts.com, including 15 speed issues, 3 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
phenixrts.com website review: scores and fixes