Website review, no card needed

influencor.com logo

influencor.com website review

Visit site (opens in a new tab)Reviewed 10 November 202635 issues · 69 checks

This review found 35 issues worth fixing on influencor.com, 8 of them high impact, across 69 checks. The most urgent: 1 image over 500 KB. 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 influencor.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. influencor.com at 0.4 s0.4 s
  2. influencor.com at 0.8 s0.8 s
  3. influencor.com at 1.2 s1.2 s
  4. influencor.com at 1.6 s1.6 s
  5. influencor.com at 2.0 s2.0 s
  6. influencor.com at 2.3 s2.3 s
  7. influencor.com at 2.7 s2.7 s
  8. influencor.com at 3.1 s3.1 s

Speed

2 to fix92
  • Use efficient cache lifetimes

    150 ms · 455 KiB

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

  • Improve image delivery

    293 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Yandex Metrica and Hotjar and others), adding 587 KiB and 279 ms of main-thread time.

  • Render-blocking requests

    200 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.

  • Reduce unused CSS

    150 ms · 20 KiB

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

  • Reduce unused JavaScript

    138 KiB

    About 138 KiB of JavaScript is downloaded but never used on this page.

  • 3 long tasks on the main thread

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

3 checks passed
  • Mobile performance score: 92

    92/100

    Your mobile performance score is 92. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 313 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

3 to fix100
  • Speed Index: 7.5 s

    7.5 s

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

  • 33 images without width and height

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

  • Time to Interactive: 5.7 s

    5.7 s

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

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

4 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.7 s

    1.7 s

    Your largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Influencers Marketing for Performance Brands”.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 52 ms

    52 ms

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

Images and page weight

5 to fix33
  • 1 image over 500 KB

    intro-animation.gif weighs 2.3 MB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    1.4 MB

    2 images are downloaded at several times the size a phone draws them, for example intro-animation.gif at 1,600 px wide, shown at 329 px. Resized copies would save about 1.4 MB.

  • Page weight: 3.5 MB in 78 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 78 requests on a phone: images 3.0 MB (45), scripts 388 KiB (16) and fonts 113 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (2.7 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.

  • 3 images below the first screen load straight away

    3 images further down the page (315 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.99 g

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

Accessibility

9 to fixGoogle 7787
  • 20 text elements with low contrast

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

  • <object> elements must have alternative text (1 element)

    <object> elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (10 elements)

    All page content should be contained by landmarks: 10 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.

  • Zoom is disabled

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

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

  • 8 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

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

SEO

9 to fixGoogle 10059
  • No H1 headline

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

  • Title is long (96 characters)

    Your title is 96 characters, so Google will cut it off around 60: “Influencor.com - Performance Brands Influencers Marketing & Influencers Monetization Mark…”.

  • No structured data

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

  • Meta description is short (40 characters)

    Your meta description is only 40 characters: “landing page template for saas companies”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

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

  • 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 XML sitemap

    No XML sitemap at https://influencor.com/sitemap.xml, so Google discovers your pages only by following links.

  • Only 1 internal link

    The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

1 checks passed
  • robots.txt in place

    robots.txt is in place.

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

Best practices

2 to fixGoogle 7389
  • 8 third-party cookies

    8 third-party cookies are 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_CONNECTION_CLOSED”.

  • 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

3 to fix67
  • 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.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 495 words of visible text.

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “PRICING REQUEST”, “CONTACT” and “GET IN TOUCH”.

  • 3 short forms

    3 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 28 testimonial or review blocks, 5 customer or partner logos and 1 trust badge.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 14 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2019.

Stack

Framework
jQuery
Hosting
WHG Hosting Services Ltd

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 influencor.com, including 5 speed issues, 9 SEO issues and 3 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