Website review, no card needed
tiff.ro website review
Visit site (opens in a new tab)Reviewed 25 October 202631 issues · 77 checks
This review found 31 issues worth fixing on tiff.ro, 10 of them high impact, across 77 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.2 s |
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 889 ms |
| Jun 6, 2026 | 762 ms |
| Jun 13, 2026 | 705 ms |
| Jun 20, 2026 | 660 ms |
| Jun 27, 2026 | 659 ms |
| Jul 4, 2026 | 659 ms |
| Jul 11, 2026 | 653 ms |
| Jul 18, 2026 | 810 ms |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 936 ms |
| Sep 26, 2026 | 909 ms |
| Oct 3, 2026 | 910 ms |
| Oct 10, 2026 | 887 ms |
| Oct 17, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 104 ms |
| May 9, 2026 | 104 ms |
| May 16, 2026 | 107 ms |
| May 23, 2026 | 108 ms |
| May 30, 2026 | 94 ms |
| Jun 6, 2026 | 89 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 88 ms |
| Jun 27, 2026 | 88 ms |
| Jul 4, 2026 | 88 ms |
| Jul 11, 2026 | 89 ms |
| Jul 18, 2026 | 91 ms |
| Jul 25, 2026 | 84 ms |
| Aug 1, 2026 | 85 ms |
| Aug 8, 2026 | 85 ms |
| Aug 15, 2026 | 85 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 87 ms |
| Sep 5, 2026 | 89 ms |
| Sep 12, 2026 | 88 ms |
| Sep 19, 2026 | 88 ms |
| Sep 26, 2026 | 89 ms |
| Oct 3, 2026 | 89 ms |
| Oct 10, 2026 | 90 ms |
| Oct 17, 2026 | 94 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
Speed
Use efficient cache lifetimes
1.8 s · 1.9 MB45 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 59). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
450 ms · 1.1 MB10 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused JavaScript
750 ms · 180 KiBAbout 180 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
900 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
4 third-party services on the page
4 third-party services load with your homepage (Facebook, Google Tag Manager and Cloudflare and others), adding 434 KiB and 391 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 163 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
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.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 543 ms of it running JavaScript. That is comfortably low.
Server response: 101 ms
101 msYour server sent the HTML in 101 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Cumulative Layout Shift: 1.028
1.028The layout shifts by 1.028 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 6.1 s
6.1 sYour largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “1”.
Time to Interactive: 7.9 s
7.9 sThe page becomes fully interactive after 7.9 s. Good is under 3.8 s.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 104 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 163 ms
163 msScripts block the page for only 163 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.9 MB in 53 requests
2.9 MBYour homepage downloads 2.9 MB in 53 requests on a phone: images 2.2 MB (31), scripts 498 KiB (8) and fonts 194 KiB (5). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (1.5 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.
About 0.8 g of CO₂ per visit
0.82 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.82 g of CO₂e: 98.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
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 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
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 (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 7 failed. 3 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
105 internal links, 35 external
The homepage links to 105 pages on tiff.ro and 35 external pages.
5 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Festivalul Internațional de Film Transilvania TIFF este primul și cel mai mare festival dedicat filmului de lungmetraj …”.
Title: 45 characters
Your title is a healthy 45 characters: “TIFF Transilvania International Film Festival”.
Canonical URL set
The canonical URL is https://tiff.ro/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://tiff.ro/sitemap.xml.
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://tiff.ro/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 (439 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://tiff.ro/en all use the title “TIFF Transilvania International Film Festival”. Search engines can't tell which page to show for a search, so each competes with the others.
11 pages without a meta description
https://tiff.ro/industry, https://tiff.ro/program, https://tiff.ro/filme, https://tiff.ro/evenimente, https://tiff.ro/abonamente and https://tiff.ro/sponsori-si-parteneri and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://tiff.ro/en and https://tiff.ro/program have 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 55 found) and read each the way a search engine does.
4 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
18 small tap targets
18 of 42 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 “Error: <svg> attribute width: Expected length, "auto".”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 347 words of copy
The homepage carries about 347 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “TIFF SHOP”.
5 calls to action
The homepage has 5 calls to action, for example “TIFF SHOP”, “Contact” and “TIFF Shop”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
4 trackers load before any consent
4Before 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
7 other companies contacted
Loading the homepage contacts 7 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 tiff.ro, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Drupal
Company
- Founded
- 2002
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on tiff.ro, including 11 speed issues, 3 SEO issues 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.