Programmable

Website review, no card needed

presumelink.com logo

presumelink.com website review

Visit site (opens in a new tab)Reviewed 10 November 202628 issues · 67 checks

This review found 28 issues worth fixing on presumelink.com, 3 of them high impact, across 67 checks. The most urgent: <html> element must have a lang attribute (1 element). 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

Site score

83B

Closest competitors among reviewed websites

Compare side by side

One score from every part of this review. How it works

www.presumelink.com (opens in a new tab)
Full-page screenshot of presumelink.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. presumelink.com at 0.4 s0.4 s
  2. presumelink.com at 0.8 s0.8 s
  3. presumelink.com at 1.3 s1.3 s
  4. presumelink.com at 1.7 s1.7 s
  5. presumelink.com at 2.1 s2.1 s
  6. presumelink.com at 2.5 s2.5 s
  7. presumelink.com at 3.0 s3.0 s
  8. presumelink.com at 3.4 s3.4 s

Speed

6 to fix86

  • Use efficient cache lifetimes

    1.1 MB

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

  • Mobile performance score: 86

    86/100

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

  • Render-blocking requests

    800 ms

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

  • Reduce unused CSS

    300 ms · 61 KiB

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

  • Main-thread work: 2.9 s

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

  • 1,902 HTML elements

    The page has 1,902 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused JavaScript

    150 ms · 223 KiB

    About 223 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 6 long tasks on the main thread

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

  • Improve image delivery

    106 KiB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Other Google APIs/SDKs), adding 101 KiB and 34 ms of main-thread time.

  • Legacy JavaScript

    14 KiB

    Polyfills for old browsers add 14 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: 3 ms

    3 ms

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

Core Web Vitals

4 to fix90

  • Time to Interactive: 6.9 s

    6.9 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • Total Blocking Time: 336 ms

    336 ms

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

  • First Contentful Paint: 2.1 s

    2.1 s

    The first text or image appears after 2.1 s on a phone. Good is under 1.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.

2 checks passed

  • Largest Contentful Paint: 2.1 s

    2.1 s

    Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Build ATS-optimized resumes, publish them under a permanent…”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix67

  • Page weight: 3.8 MB in 91 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 91 requests on a phone: images 2.9 MB (33), scripts 509 KiB (22) and fonts 309 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.09 g

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

Accessibility

6 to fixGoogle 9175

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • No main landmark

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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 36 text elements with low contrast

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

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (3 elements).

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (32 elements).

  • Headings skip levels

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

2 checks passed

  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 7 automated accessibility rules passed

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

SEO

Google 100100

  • 50 internal links, 0 external

    The homepage links to 50 pages on presumelink.com and 0 external pages.

8 checks passed

  • Meta description: 92 characters

    Your meta description is 92 characters: “Build ATS-friendly resumes, get a permanent shareable link, and apply for jobs in one place.”.

  • One H1 headline

    Your main headline reads: “Presume link.”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “PresumeLink — One link. Your entire career.”.

  • Canonical URL set

    The canonical URL is https://presumelink.com/.

  • Structured data in place

    Structured data found: Organization, WebApplication and WebSite.

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

AI search readiness

100

  • No llms.txt

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.

Other pages

4 to fix79

  • 2 linked pages hidden from search

    https://www.presumelink.com/resume-builder and https://www.presumelink.com/analytics are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.presumelink.com/resume-builder and https://www.presumelink.com/analytics all use the title “Log in | PresumeLink”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.presumelink.com/resume-builder and https://www.presumelink.com/analytics use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://www.presumelink.com/resume-builder, https://www.presumelink.com/analytics, https://www.presumelink.com/help, https://www.presumelink.com/contact, https://www.presumelink.com/privacy-policy and https://www.presumelink.com/data-privacy and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 internal pages checked

    We fetched 7 pages linked from your homepage and read each the way a search engine does.

4 checks passed

  • Linked pages load

    All 7 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 7 pages that loaded have a meta description.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9689

  • 1 JavaScript error while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50

  • 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 social proof

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

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

  • Only about 17 words

    The homepage has only about 17 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

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

2 checks passed

  • 4 calls to action

    The homepage has 4 calls to action, for example “Start session”, “Start a chat” and “Get started for free”.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

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

  • 1 other company contacted

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on presumelink.com, including 10 speed issues and 5 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