Website review, no card needed
evjfaparis.fr website review
Visit site (opens in a new tab)Reviewed 12 November 202641 issues · 78 checks
This review found 41 issues worth fixing on evjfaparis.fr, 13 of them high impact, across 78 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
63DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
2.3 s · 1.9 MB54 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Reduce unused JavaScript
1.8 s · 577 KiBAbout 577 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
864 KiB7 images could be 864 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
5 third-party services on the page
5 third-party services load with your homepage (weezevent.com, Google Tag Manager and Google Analytics and others), adding 1.8 MB and 654 ms of main-thread time.
weezevent.com adds 504 ms
504 msweezevent.com costs a phone 504 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 263 ms. During a long task the page ignores taps.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Reduce unused CSS
63 KiBAbout 63 KiB of CSS is downloaded but never applied on this page.
Minify CSS
11 KiB11 KiB could be saved by minifying CSS.
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: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 629 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.0 s
12.0 sYour largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 15.3 s
15.3 sThe page becomes fully interactive after 15.3 s. Good is under 3.8 s.
Speed Index: 7.0 s
7.0 sVisually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 310 ms
310 msScripts block taps and scrolling for 310 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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.3 MB in 87 requests
3.3 MBYour homepage downloads 3.3 MB in 87 requests on a phone: scripts 1.4 MB (31), images 1.2 MB (23) and fonts 471 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (79 KiB) is 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.
1 image below the first screen load straight away
1 image further down the page (79 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.93 g of CO₂e: 111.4 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
7 text elements with low contrast
7 text elements don'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.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (33 elements)
All page content should be contained by landmarks: 33 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.
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.
16 links without text
16 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
25 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 25 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (94 characters)
Your title is 94 characters, so Google will cut it off around 60: “Photographe EVJF / Anniversaire pas cher Paris| Enterrement Vie de Jeune Fille - Future M…”.
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.
Meta description is long (243 characters)
Your meta description is 243 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://evjfaparis.fr/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at evjfaparis.fr/robots.txt, the first file search crawlers ask for.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
11 internal links, 8 external
The homepage links to 11 pages on evjfaparis.fr and 8 external pages.
1 checks passed
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
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://evjfaparis.fr/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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (807 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages are broken
Your homepage links to https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-paris, https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-photopro and https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-photo-evjf, which answer with an error. Visitors hit a dead end and search engines drop them.
9 pages share 2 titles
/, https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-mariee and https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-photo-shooting all use the title “Photographe EVJF / Anniversaire pas cher Paris| Enterrement Vie de Je…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages share a meta description
https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-photo, https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-photo-prix, https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-shooting, https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-mariee, https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-photo-demoiselles-dhonneur and https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-photo-album and 2 others use the same meta description. A description written for each page earns more clicks.
7 pages without an H1
https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-photo, https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-photo-prix, https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-shooting, https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-photo-demoiselles-dhonneur, https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-photo-album and https://evjfaparis.fr/photographe-pas-cher-paris-evjf-tarifs-future-mariee-photo-shooting and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 8 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 8 pages that loaded have a <title>.
Best practices
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
6 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 809 words of copy
The homepage carries about 809 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before 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.
2 cookies set on arrival
2Opening 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.
8 other companies contacted
Loading the homepage contacts 8 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 evjfaparis.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- OVHcloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on evjfaparis.fr, including 13 speed issues, 8 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.