Website review, no card needed

1409media.com logo

1409media.com website review

Visit site (opens in a new tab)Reviewed 22 November 202636 issues · 77 checks

This review found 36 issues worth fixing on 1409media.com, 7 of them high impact, across 77 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

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

How it loaded on a phone

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

Speed

11 to fix50
  • Reduce unused JavaScript

    6.1 s · 790 KiB

    About 790 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.1 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Squarespace, Google CDN and Google Tag Manager and others), adding 2.4 MB and 942 ms of main-thread time.

  • Mobile performance score: 50

    50/100

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

  • Squarespace adds 378 ms

    378 ms

    Squarespace costs a phone 378 ms of main-thread work and 799 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.

  • Google CDN adds 376 ms

    376 ms

    Google CDN costs a phone 376 ms of main-thread work and 742 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

    300 ms · 87 KiB

    About 87 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.

  • Legacy JavaScript

    300 ms · 48 KiB

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

  • Render-blocking requests

    300 ms

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

  • Main-thread work: 2.0 s

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

  • Adobe TypeKit adds 8 ms

    8 ms

    Adobe TypeKit costs a phone 8 ms of main-thread work and 382 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.

  • squarespace-cdn.com adds 0 ms

    0 ms

    squarespace-cdn.com costs a phone 0 ms of main-thread work and 312 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.

  • 7 long tasks on the main thread

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

  • Improve image delivery

    150 ms · 36 KiB

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

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    17 KiB

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

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

    27 ms

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

Core Web Vitals

6 to fix60
  • First Contentful Paint: 10.3 s

    10.3 s

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

  • Largest Contentful Paint: 17.2 s

    17.2 s

    Your largest element takes 17.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “1409 MEDIA”.

  • Time to Interactive: 17.4 s

    17.4 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Total Blocking Time: 300 ms

    300 ms

    Scripts block taps and scrolling for 300 ms in total while the page loads. 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.

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.9 MB in 72 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 72 requests on a phone: scripts 1.6 MB (32), other files 469 KiB (3) and fonts 418 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.84 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.84 g of CO₂e: 100.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

6 to fixGoogle 9492
  • 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.

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

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

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

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

4 to fixGoogle 10079
  • Title is short (10 characters)

    Your title is only 10 characters: “1409 MEDIA”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (45 characters)

    Your meta description is only 45 characters: “Modernistic Digital Photography & Videography”. 70 to 160 characters is enough to sell the click.

  • 7 H1 headlines

    There are 7 <h1> headlines (“”, “WHO WE ARE” and “WHO WE ARE”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/57229b937c65e4ea4ab…”.

  • 12 internal links, 4 external

    The homepage links to 12 pages on 1409media.com and 4 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is http://www.1409media.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 http://www.1409media.com/sitemap.xml.

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://www.1409media.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 (620 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.1409media.com/contact-us has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages with very little text

    https://www.1409media.com/the-portfolio, https://www.1409media.com/packages, https://www.1409media.com/blog and https://www.1409media.com/contact-us have 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.

  • 5 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • 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 5 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 2 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/sitecss/57229b937c65e4ea4abcb2f8/75/515c7bd0e4b054d…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 3 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 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 562 words of copy

    The homepage carries about 562 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “CONTACT US” and “Sign Up”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 6 cookies set on arrival

    6

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

  • 11 other companies contacted

    Loading the homepage contacts 11 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 1409media.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
Squarespace
Analytics
Google Analytics
Hosting
Squarespace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on 1409media.com, including 17 speed issues, 4 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