Website review, no card needed

dailypress.com logo

dailypress.com website review

Visit site (opens in a new tab)Reviewed 4 November 202626 issues · 65 checks

This review found 26 issues worth fixing on dailypress.com, 7 of them high impact, across 65 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
3.4 s3.2 sMay 16Oct 313.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.2 s
May 23, 20263.2 s
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.3 s
Jun 27, 20263.3 s
Jul 4, 20263.3 s
Jul 11, 20263.4 s
Jul 18, 20263.3 s
Jul 25, 20263.3 s
Aug 1, 20263.3 s
Aug 8, 20263.3 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.3 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.3 s
Oct 17, 20263.3 s
Oct 24, 20263.3 s
Oct 31, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
207 ms180 msMay 16Oct 31194 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026196 ms
May 23, 2026196 ms
May 30, 2026193 ms
Jun 6, 2026193 ms
Jun 13, 2026192 ms
Jun 20, 2026192 ms
Jun 27, 2026197 ms
Jul 4, 2026204 ms
Jul 11, 2026203 ms
Jul 18, 2026202 ms
Jul 25, 2026196 ms
Aug 1, 2026195 ms
Aug 8, 2026196 ms
Aug 15, 2026196 ms
Aug 22, 2026194 ms
Aug 29, 2026193 ms
Sep 5, 2026194 ms
Sep 12, 2026194 ms
Sep 19, 2026189 ms
Sep 26, 2026185 ms
Oct 3, 2026183 ms
Oct 10, 2026184 ms
Oct 17, 2026188 ms
Oct 24, 2026192 ms
Oct 31, 2026194 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

5 to fix33
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user CLS: 0.15

    0.15

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 837 ms

    837 ms

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

1 checks passed
  • Real-user INP: 194 ms

    194 ms

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

Images and page weight

3 to fix53
  • Page weight: 5.5 MB

    5.5 MB

    Your homepage downloads 5.5 MB on a phone, 1.5 MB of it images (28%). Under 2 MB keeps phones on slow connections fast.

  • 15 images below the first screen load straight away

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

  • 4 images far larger than shown

    212 KiB

    4 images are downloaded at several times the size a phone draws them, for example image at 500 px wide, shown at 55 px. Resized copies would save about 212 KiB.

  • 10 images in older formats

    10 images (460 KiB) 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.

  • About 1.6 g of CO₂ per visit

    1.55 g

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

Accessibility

6 to fix91
  • Images must have alternative text (15 elements)

    Images must have alternative text: 15 elements on the page fail this check, rated critical by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

  • 1 form field without a label

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

3 to fix83
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Daily Press - Virginia News, Sports, Weather, Business & Things to Do”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Daily Press” and “”). One clear main headline is easier for people and search engines.

  • Meta description is long (263 characters)

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

  • No X (Twitter) card tag

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

  • 238 internal links, 68 external

    The homepage links to 238 pages on dailypress.com and 68 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: LocalBusiness and NewsMediaOrganization.

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

AI search readiness

1 to fix65
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No llms.txt

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

2 checks passed
  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,682 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix88
  • 6 pages without a meta description

    https://www.dailypress.com/util-clean-cookies, https://www.dailypress.com/news, https://www.dailypress.com/tag/military, https://www.dailypress.com/location/virginia/gloucester-county, https://www.dailypress.com/location/virginia/hampton and https://www.dailypress.com/location/virginia/newport-news have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.dailypress.com/latest-headlines and https://www.dailypress.com/local-news use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.dailypress.com/util-clean-cookies has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.dailypress.com/util-clean-cookies has 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 139 found) and read each the way a search engine does.

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

  • 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 fix78
  • 4 broken images

    4 images failed to load on a phone, for example https://rtb.mfadsrvr.com/sync?ssp=revcontent&ssp_user_id=fc071bceeb5144f3a7ca7a193f530268&gpp=DBACOe~CQtKJcAQtKJcAEX1iAENC3FgAAAAAEPgACiQAAAUlgIgAVAA4ACQAGgARQAmABoAEcAK0AZYBAACDgLzAaKA5YB8YFJQAAAA.IL.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Sailthru is not defined”.

2 checks passed
  • Tap targets are thumb-sized

    119 of 127 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • 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: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Subscribe Now” and “Contact the newsroom”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Subscribe Now”, “Contact the newsroom” and “Buy Photos”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 3 mores (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

  • 36 cookies set on arrival

    36

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

  • 90 other companies contacted

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

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) 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 dailypress.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
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
WordPress.com

Hiring

Hiring
1 open role
Job board
careers page

Company

Founded
1896

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on dailypress.com, including 5 speed issues, 3 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