Website review, no card needed

closerstillmedia.com logo

closerstillmedia.com website review

Visit site (opens in a new tab)Reviewed 3 November 202645 issues · 92 checks

This review found 45 issues worth fixing on closerstillmedia.com, 17 of them high impact, across 92 checks. The most urgent: render-blocking requests. 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

Real-visitor load time (LCP)75th percentile, phones
3.5 s1.9 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.3 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.7 s
Jul 18, 20262.9 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.3 s
Aug 15, 20263.3 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Oct 17, 20262.2 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
218 ms160 msMay 16Oct 31179 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026169 ms
May 23, 2026167 ms
May 30, 2026176 ms
Jun 6, 2026190 ms
Jun 13, 2026195 ms
Jun 20, 2026187 ms
Jun 27, 2026187 ms
Jul 4, 2026181 ms
Jul 11, 2026168 ms
Jul 18, 2026183 ms
Jul 25, 2026181 ms
Aug 1, 2026173 ms
Aug 8, 2026211 ms
Aug 15, 2026190 ms
Aug 22, 2026199 ms
Aug 29, 2026205 ms
Sep 5, 2026191 ms
Sep 12, 2026178 ms
Sep 19, 2026172 ms
Sep 26, 2026173 ms
Oct 3, 2026186 ms
Oct 10, 2026187 ms
Oct 17, 2026188 ms
Oct 24, 2026183 ms
Oct 31, 2026179 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

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

Full-page screenshot of closerstillmedia.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. closerstillmedia.com at 0.5 s0.5 s
  2. closerstillmedia.com at 1.0 s1.0 s
  3. closerstillmedia.com at 1.5 s1.5 s
  4. closerstillmedia.com at 2.0 s2.0 s
  5. closerstillmedia.com at 2.5 s2.5 s
  6. closerstillmedia.com at 3.0 s3.0 s
  7. closerstillmedia.com at 3.5 s3.5 s
  8. closerstillmedia.com at 4.0 s4.0 s

Speed

13 to fix23
  • Render-blocking requests

    28.5 s

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

  • Mobile performance score: 23

    23/100

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

  • Main-thread work: 6.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (asp.events, Google Tag Manager and Facebook and others), adding 14.0 MB and 2.5 s of main-thread time.

  • asp.events adds 920 ms

    920 ms

    asp.events costs a phone 920 ms of main-thread work and 12.3 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.

  • Use efficient cache lifetimes

    906 KiB

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

  • Improve image delivery

    895 KiB

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

  • Google Tag Manager adds 663 ms

    663 ms

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

  • Reduce unused CSS

    600 ms · 130 KiB

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

  • Reduce unused JavaScript

    714 KiB

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

  • 20 long tasks on the main thread

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

  • Facebook adds 282 ms

    282 ms

    Facebook costs a phone 282 ms of main-thread work and 307 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.

  • 2,115 HTML elements

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

  • Legacy JavaScript

    60 KiB

    Polyfills for old browsers add 60 KiB JavaScript that modern phones do not need.

  • Font display

    50 ms

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

  • Minify JavaScript

    21 KiB

    21 KiB could be saved by minifying JavaScript.

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

    2 ms

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

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • First Contentful Paint: 28.8 s

    28.8 s

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

  • Largest Contentful Paint: 28.8 s

    28.8 s

    Your largest element takes 28.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We Are CloserStill. Our 120+ award-winning events connect b…”.

  • Speed Index: 28.8 s

    28.8 s

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

  • Time to Interactive: 52.3 s

    52.3 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • Real-user CLS: 0.19

    0.19

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Cumulative Layout Shift: 0.162

    0.162

    The layout shifts by 0.162 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 169 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -7%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

    Real visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 182 ms

    182 ms

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

  • Real-user TTFB: 662 ms

    662 ms

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

Images and page weight

3 to fix43
  • Page weight: 23.3 MB in 152 requests

    23.3 MB

    Your homepage downloads 23.3 MB in 152 requests on a phone: media 13.8 MB (1), scripts 7.0 MB (55) and images 1.7 MB (32). Under 2 MB keeps phones on slow connections fast.

  • 5 images far larger than shown

    813 KiB

    5 images are downloaded at several times the size a phone draws them, for example DSC_2614A.jpg at 2,333 px wide, shown at 332 px. Resized copies would save about 813 KiB.

  • 13 images below the first screen load straight away

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

  • About 6.6 g of CO₂ per visit

    6.59 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 8993
  • 5 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

  • 7 links without text

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

  • 1 form field without a label

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h5), 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.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 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 9272
  • No H1 headline

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

  • 105 links crawlers can't follow

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

  • Title is short (17 characters)

    Your title is only 17 characters: “CloserStill Media”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (190 characters)

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

  • Structured data has 1 problem

    Structured data found (Event, Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://www.closerstillmedia.com/includes/images/profiles/ico_group.png")”.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 50 internal links, 22 external

    The homepage links to 50 pages on closerstillmedia.com and 22 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.closerstillmedia.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.closerstillmedia.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    21%

    A phone browser shows 2,418 words, but the HTML your server sends has only 505. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing url, 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.closerstillmedia.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.

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

Other pages

100
  • 1 page slow to respond

    https://www.closerstillmedia.com/closerlook took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

7 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 1 page that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://c1.adform.net/serving/cookie/match?party=1173.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Unsafe attempt to load URL https://themes.asp.events/_base/1-2-0/includes/icons/general.svg from frame with URL https:/…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    22 of 26 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 2 customer or partner logos. 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 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 2,418 words of copy

    The homepage carries about 2,418 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Join Our Team” and “Contact Us”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 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.

  • 53 other companies contacted

    Loading the homepage contacts 53 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 closerstillmedia.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
SHOWOFF by ASP.events
Framework
jQuery
Analytics
Google Tag Manager
Hosting
AWS

Hiring

Hiring
6 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on closerstillmedia.com, including 22 speed issues, 5 SEO issues and 4 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