Website review, no card needed

48hourfilm.com logo

48hourfilm.com website review

Visit site (opens in a new tab)Reviewed 18 October 202640 issues · 83 checks

This review found 40 issues worth fixing on 48hourfilm.com, 11 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. 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.7 s2.7 sApr 25Oct 103.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.8 s
May 2, 20262.9 s
May 9, 20262.9 s
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20263.0 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.3 s
Aug 8, 20263.3 s
Aug 15, 20263.5 s
Aug 22, 20263.5 s
Aug 29, 20263.6 s
Sep 5, 20263.4 s
Sep 12, 20263.2 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.4 s
Oct 10, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
95 ms85 msApr 25Oct 1093 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202688 ms
May 2, 202687 ms
May 9, 202687 ms
May 16, 202691 ms
May 23, 202691 ms
May 30, 202691 ms
Jun 6, 202692 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202690 ms
Jul 4, 202687 ms
Jul 11, 202688 ms
Jul 18, 202690 ms
Jul 25, 202688 ms
Aug 1, 202692 ms
Aug 8, 202694 ms
Aug 15, 202689 ms
Aug 22, 202688 ms
Aug 29, 202688 ms
Sep 5, 202686 ms
Sep 12, 202686 ms
Sep 19, 202688 ms
Sep 26, 202688 ms
Oct 3, 202690 ms
Oct 10, 202693 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 48hourfilm.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 48hourfilm.com at 0.4 s0.4 s
  2. 48hourfilm.com at 0.8 s0.8 s
  3. 48hourfilm.com at 1.1 s1.1 s
  4. 48hourfilm.com at 1.5 s1.5 s
  5. 48hourfilm.com at 1.9 s1.9 s
  6. 48hourfilm.com at 2.3 s2.3 s
  7. 48hourfilm.com at 2.6 s2.6 s
  8. 48hourfilm.com at 3.0 s3.0 s

Speed

6 to fix72
  • Use efficient cache lifetimes

    29.9 s · 16.8 MB

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

  • Improve image delivery

    23.6 s · 4.8 MB

    5 images could be 4.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 23.6 s faster on a phone.

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72 (desktop: 71). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    700 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 700 ms.

  • Reduce unused JavaScript

    300 ms · 252 KiB

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

  • Font display

    350 ms

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

  • Duplicated JavaScript

    250 ms · 13 KiB

    13 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 250 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.

  • 2 third-party services on the page

    2 third-party services load with your homepage (JSDelivr CDN and Unpkg), adding 25 KiB and 51 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 0.5 s

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

  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 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.

  • Real-user FCP: 3.4 s

    3.4 s

    Real visitors see the first content after 3.4 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: 31.4 s

    31.4 s

    Your largest element takes 31.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Worlds Largest Filmmaking Competition START YOUR JOURNEY”.

  • Time to Interactive: 31.4 s

    31.4 s

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Largest content (LCP) got 21% slower for real visitors

    +21%

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

  • Speed Index: 4.6 s

    4.6 s

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

5 checks passed
  • Real-user INP: 79 ms

    79 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • First Contentful Paint: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.011

    0.011

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

  • Total Blocking Time: 12 ms

    12 ms

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

Images and page weight

4 to fix43
  • Page weight: 17.1 MB in 33 requests

    17.1 MB

    Your homepage downloads 17.1 MB in 33 requests on a phone: media 9.8 MB (2), images 6.8 MB (19) and scripts 310 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 17 images in older formats

    17 images (1.6 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.

  • 7 images below the first screen load straight away

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

  • 2 images far larger than shown

    171 KiB

    2 images are downloaded at several times the size a phone draws them, for example 5_Eindhoven2023-OldSaints.jpg at 1,080 px wide, shown at 164 px. Resized copies would save about 171 KiB.

  • About 4.8 g of CO₂ per visit

    4.84 g

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

Accessibility

6 to fixGoogle 8392
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 3 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • ARIA role should be appropriate for the element (3 elements)

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

2 checks passed
  • Every image has alt text

    All 26 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. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 10078
  • Title is short (20 characters)

    Your title is only 20 characters: “48 Hour Film Project”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 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://48hourfilm.com/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 63 internal links, 16 external

    The homepage links to 63 pages on 48hourfilm.com and 16 external pages.

3 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “A fast-paced weekend in which teams compete to create the best short film in only 48 hours, using required elements. Th…”.

  • One H1 headline

    Your main headline reads: “The 48 Hour Film Project Experience”.

  • 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 https://48hourfilm.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.

  • Text is in the HTML

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

Other pages

3 to fix86
  • 4 pages share a title

    /, https://48hourfilm.com/en, https://48hourfilm.com/fr and https://48hourfilm.com/nl all use the title “48 Hour Film Project”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages share a meta description

    https://48hourfilm.com/about, https://48hourfilm.com/how-it-works, https://48hourfilm.com/genres, https://48hourfilm.com/elements, https://48hourfilm.com/rules and https://48hourfilm.com/documents and 6 others use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://48hourfilm.com/events has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://48hourfilm.com/events 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 29 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 9 small tap targets

    9 of 16 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: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • No social proof

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

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

  • No analytics detected

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

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

    The homepage carries about 458 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START YOUR JOURNEY”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Register”, “Start Your Journey” and “How to Register”.

  • Direct contact links

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

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts 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 48hourfilm.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
Tailwind CSS

Company

Founded
2005

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on 48hourfilm.com, including 15 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