Website review, no card needed
flytographer.com website review
Visit site (opens in a new tab)Reviewed 21 October 202635 issues · 83 checks
This review found 35 issues worth fixing on flytographer.com, 14 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 104 ms |
| May 9, 2026 | 104 ms |
| May 16, 2026 | 104 ms |
| May 23, 2026 | 104 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 105 ms |
| Jul 18, 2026 | 108 ms |
| Jul 25, 2026 | 108 ms |
| Aug 1, 2026 | 106 ms |
| Aug 8, 2026 | 106 ms |
| Aug 15, 2026 | 106 ms |
| Aug 22, 2026 | 106 ms |
| Aug 29, 2026 | 112 ms |
| Sep 5, 2026 | 112 ms |
| Sep 12, 2026 | 115 ms |
| Sep 19, 2026 | 117 ms |
| Sep 26, 2026 | 118 ms |
| Oct 3, 2026 | 119 ms |
| Oct 10, 2026 | 115 ms |
| Oct 17, 2026 | 113 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
How it loaded on a phone
0.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.7 s
3.2 s
3.7 s
Speed
Use efficient cache lifetimes
1.4 s · 4.0 MB26 files are served with short cache lifetimes, so returning visitors download them again (4.0 MB).
Reduce unused JavaScript
1.9 s · 751 KiBAbout 751 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Improve image delivery
500 ms · 3.6 MB28 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (frontapp.com, Wistia and Google Tag Manager and others), adding 9.9 MB and 1.3 s of main-thread time.
Wistia adds 395 ms
395 msWistia costs a phone 395 ms of main-thread work and 7.7 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.
Mobile performance score: 53
53/100Your mobile performance score is 53 (desktop: 67). Pages that score under 90 lose visitors before the first paint.
frontapp.com adds 415 ms
415 msfrontapp.com costs a phone 415 ms of main-thread work and 1.5 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 401 ms. During a long task the page ignores taps.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 265 ms
265 msGoogle Tag Manager costs a phone 265 ms of main-thread work and 377 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.
1,823 HTML elements
The page has 1,823 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 55 KiBPolyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
200 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
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: 24 ms
24 msYour server sent the HTML in 24 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 24.9 s
24.9 sYour largest element takes 24.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A smiling couple holds their son on their shoulders in Rome…”.
Time to Interactive: 27.7 s
27.7 sThe page becomes fully interactive after 27.7 s. Good is under 3.8 s.
First Contentful Paint: 7.5 s
7.5 sThe first text or image appears after 7.5 s on a phone. Good is under 1.8 s.
Speed Index: 11.4 s
11.4 sVisually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 848 ms
848 msReal visitors wait 848 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 104 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 129 ms
129 msReal visitors wait 129 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 188 ms
188 msScripts block the page for only 188 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 18.0 MB in 139 requests
18.0 MBYour homepage downloads 18.0 MB in 139 requests on a phone: media 10.9 MB (3), images 4.0 MB (34) and scripts 1.8 MB (52). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
hoi-an-review-500.jpeg weighs 658 KiB. On a phone connection a single image that size takes seconds.
17 images in older formats
17 images (3.8 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.
14 images below the first screen load straight away
14 images further down the page (3.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
family-smiling-in-rome_1024.jpeg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 5.1 g of CO₂ per visit
5.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.11 g of CO₂e: 613.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
20 buttons without a name
20 buttons have no accessible name, so screen readers announce just “button”.
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 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.
Headings skip levels
Headings skip levels (h1 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 130 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
82 internal links, 14 external
The homepage links to 82 pages on flytographer.com and 14 external pages.
8 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Book local photographers in 350+ cities worldwide. Capture family vacations, surprise proposals and bucket list trips. …”.
One H1 headline
Your main headline reads: “The Best Souvenir You'll Bring Home”.
Title: 50 characters
Your title is a healthy 50 characters: “Professional Vacation Photographers | Flytographer”.
Canonical URL set
The canonical URL is https://www.flytographer.com/.
Structured data in place
Structured data found: Organization 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.
XML sitemap found
Your XML sitemap is reachable at https://www.flytographer.com/sitemap.xml.
AI search readiness
4 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: 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,190 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.flytographer.com/llms.txt (1 KiB, 2 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.flytographer.com/welcome-gift is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without an H1
https://www.flytographer.com/welcome-gift has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 51 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.
2 checks passed
Tap targets are thumb-sized
5 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,152 words of copy
The homepage carries about 1,152 words of visible text.
4 checks passed
18 calls to action
The homepage has 18 calls to action, for example “Pricing”, “Book Nowchevron_right” and “Contact Us”.
Social proof on the page
Social proof on the homepage: 60 testimonial or review blocks, 16 customer or partner logos, a star rating and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo, Meta Pixel and Reddit Pixel (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
23 other companies contacted
Loading the homepage contacts 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 flytographer.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
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Heroku
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on flytographer.com, including 18 speed issues, 1 SEO issue and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.