Website review, no card needed

filmdaily.co logo

filmdaily.co website review

Visit site (opens in a new tab)Reviewed 28 October 202644 issues · 84 checks

This review found 44 issues worth fixing on filmdaily.co, 21 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
5.0 s4.2 sMay 9Oct 244.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.7 s
May 16, 20264.7 s
May 23, 20264.7 s
May 30, 20264.5 s
Jun 6, 20264.4 s
Jun 13, 20264.5 s
Jun 20, 20264.4 s
Jun 27, 20264.3 s
Jul 4, 20264.4 s
Jul 11, 20264.3 s
Jul 18, 20264.3 s
Jul 25, 20264.4 s
Aug 1, 20264.4 s
Aug 8, 20264.5 s
Aug 15, 20264.5 s
Aug 22, 20264.5 s
Aug 29, 20264.5 s
Sep 5, 20264.6 s
Sep 12, 20264.5 s
Sep 19, 20264.6 s
Sep 26, 20264.7 s
Oct 3, 20264.7 s
Oct 10, 20264.9 s
Oct 17, 20264.7 s
Oct 24, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
281 ms179 msMay 9Oct 24192 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026222 ms
May 16, 2026222 ms
May 23, 2026219 ms
May 30, 2026213 ms
Jun 6, 2026206 ms
Jun 13, 2026200 ms
Jun 20, 2026209 ms
Jun 27, 2026191 ms
Jul 4, 2026210 ms
Jul 11, 2026219 ms
Jul 18, 2026221 ms
Jul 25, 2026249 ms
Aug 1, 2026256 ms
Aug 8, 2026244 ms
Aug 15, 2026235 ms
Aug 22, 2026241 ms
Aug 29, 2026249 ms
Sep 5, 2026267 ms
Sep 12, 2026269 ms
Sep 19, 2026260 ms
Sep 26, 2026253 ms
Oct 3, 2026239 ms
Oct 10, 2026226 ms
Oct 17, 2026211 ms
Oct 24, 2026192 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 filmdaily.co (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. filmdaily.co at 1.7 s1.7 s
  2. filmdaily.co at 3.5 s3.5 s
  3. filmdaily.co at 5.2 s5.2 s
  4. filmdaily.co at 7.0 s7.0 s
  5. filmdaily.co at 8.7 s8.7 s
  6. filmdaily.co at 10.5 s10.5 s
  7. filmdaily.co at 12.2 s12.2 s
  8. filmdaily.co at 14.0 s14.0 s

Speed

11 to fix15
  • Reduce unused JavaScript

    5.2 s · 1.0 MB

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

  • Use efficient cache lifetimes

    2.3 s · 415 KiB

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

  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 15

    15/100

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

  • Main-thread work: 5.2 s

    A phone's processor spends 5.2 s on main-thread work while loading, 2.3 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 (Google/Doubleclick Ads, Google Tag Manager and Facebook and others), adding 2.0 MB and 1.6 s of main-thread time.

  • Google/Doubleclick Ads adds 676 ms

    676 ms

    Google/Doubleclick Ads costs a phone 676 ms of main-thread work and 796 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

    630 ms · 115 KiB

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

  • Improve image delivery

    550 ms · 104 KiB

    6 images could be 104 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

  • Google Tag Manager adds 569 ms

    569 ms

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

  • Font display

    350 ms

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

  • 15 long tasks on the main thread

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

  • Minify JavaScript

    70 ms · 5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    50 ms · 21 KiB

    Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

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

    60 ms

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

Core Web Vitals

13 to fix0
  • 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.

  • Real-user LCP: 8.5 s

    8.5 s

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

  • Real-user CLS: 0.67

    0.67

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

  • Real-user FCP: 5.8 s

    5.8 s

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

  • Real-user TTFB: 2.8 s

    2.8 s

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

  • Largest Contentful Paint: 23.6 s

    23.6 s

    Your largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Nate Silver’s Twitter account ignites election buzz, drawin…”. Most of its time is resource load delay (11.4 s).

  • Time to Interactive: 23.6 s

    23.6 s

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

  • Speed Index: 13.1 s

    13.1 s

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

  • First Contentful Paint: 6.0 s

    6.0 s

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

  • Cumulative Layout Shift: 0.492

    0.492

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

  • Total Blocking Time: 816 ms

    816 ms

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

  • Real-user INP: 231 ms

    231 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 222 ms to 192 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-24, real Chrome visitors' largest content (lcp) went from 4.7 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

1 to fix70
  • Page weight: 7.7 MB in 179 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 179 requests on a phone: media 4.6 MB (1), scripts 2.0 MB (68) and fonts 412 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 2.2 g of CO₂ per visit

    2.18 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

7 to fixGoogle 8792
  • 8 text elements with low contrast

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

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

    All page content should be contained by landmarks: 25 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 form fields without a label

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

  • 3 links without text

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

2 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 9277
  • No H1 headline

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

  • Title is short (17 characters)

    Your title is only 17 characters: “Home – Film Daily”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No XML sitemap

    No XML sitemap at https://filmdaily.co/sitemap_index.xml, so Google discovers your pages only by following links.

  • 2 links crawlers can't follow

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

  • 148 internal links, 3 external

    The homepage links to 148 pages on filmdaily.co and 3 external pages.

5 checks passed
  • Meta description: 86 characters

    Your meta description is 86 characters: “Always now, forever independent. Film Daily keeps you entertained about entertainment.”.

  • Canonical URL set

    The canonical URL is https://filmdaily.co/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.

AI search readiness

100
  • No llms.txt

    There is no https://filmdaily.co/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.

3 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 sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 3 linked pages hidden from search

    https://filmdaily.co/category/news, https://filmdaily.co/category/obsessions and https://filmdaily.co/category/memes are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://filmdaily.co/category/news, https://filmdaily.co/category/obsessions, https://filmdaily.co/lifestyle and https://filmdaily.co/category/memes have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page slow to respond

    https://filmdaily.co/category/memes took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    4 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

3 to fixGoogle 10071
  • 10 broken images

    10 images failed to load on a phone, for example https://filmdaily.co/.

  • 9 small tap targets

    9 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 777 words of copy

    The homepage carries about 777 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: “Subscribe”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us” and “Subscribe”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 16 cookies set on arrival

    16

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

  • 24 other companies contacted

    Loading the homepage contacts 24 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 filmdaily.co, 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
E-commerce
WooCommerce
Analytics
Google Tag Manager
Hosting
Inmotion

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on filmdaily.co, including 24 speed issues, 4 SEO issues and 2 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