Website review, no card needed
izocam.com.tr website review
Visit site (opens in a new tab)Reviewed 4 November 202646 issues · 92 checks
This review found 46 issues worth fixing on izocam.com.tr, 20 of them high impact, across 92 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 146 ms |
| May 23, 2026 | 141 ms |
| May 30, 2026 | 140 ms |
| Jun 6, 2026 | 137 ms |
| Jun 13, 2026 | 140 ms |
| Jun 20, 2026 | 140 ms |
| Jun 27, 2026 | 141 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 143 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 149 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 153 ms |
| Sep 5, 2026 | 152 ms |
| Sep 12, 2026 | 152 ms |
| Sep 19, 2026 | 151 ms |
| Sep 26, 2026 | 150 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 153 ms |
| Oct 17, 2026 | 153 ms |
| Oct 24, 2026 | 153 ms |
| Oct 31, 2026 | 154 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.9 s
1.7 s
2.6 s
3.5 s
4.3 s
5.2 s
6.1 s
6.9 s
Speed
Use efficient cache lifetimes
1.9 s · 14.0 MB57 files are served with short cache lifetimes, so returning visitors download them again (14.0 MB).
Improve image delivery
1.1 s · 6.7 MB21 images could be 6.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.5 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.3 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
300 ms · 635 KiBAbout 635 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
850 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 850 ms).
Google Tag Manager adds 701 ms
701 msGoogle Tag Manager costs a phone 701 ms of main-thread work and 491 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 · 49 KiBAbout 49 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 333 ms. During a long task the page ignores taps.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 284 ms
284 msGoogle CDN costs a phone 284 ms of main-thread work and 380 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.
Facebook adds 250 ms
250 msFacebook costs a phone 250 ms of main-thread work and 224 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.
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
Minify CSS
9 KiB9 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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 96 ms
96 msYour server sent the HTML in 96 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.
Real-user CLS: 0.34
0.34For real visitors the layout shifts by 0.34 (75th percentile). Good is under 0.1.
Time to Interactive: 20.6 s
20.6 sThe page becomes fully interactive after 20.6 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 6.0 s
6.0 sYour largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Cumulative Layout Shift: 0.507
0.507The layout shifts by 0.507 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 768 ms
768 msScripts block taps and scrolling for 768 ms in total while the page loads. Good is under 200 ms.
Real-user TTFB: 861 ms
861 msReal visitors wait 861 ms for your server to start answering (75th percentile). Good is under 800 ms.
33 images without width and height
33 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 146 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 181 ms
181 msReal visitors wait 181 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
7 images over 500 KB
7 images weigh 30.0 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
22.8 MB2 images are downloaded at several times the size a phone draws them, for example 75434.jpg at 4,501 px wide, shown at 390 px. Resized copies would save about 22.8 MB.
Page weight: 15.2 MB in 97 requests
15.2 MBYour homepage downloads 15.2 MB in 97 requests on a phone: images 13.5 MB (44), scripts 1.4 MB (24) and fonts 176 KiB (2). Under 2 MB keeps phones on slow connections fast.
16 images in older formats
16 images (33.4 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.
An image on the first screen is lazy-loaded
ekstrude-polistiren-(xps)37435.webp 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 4.3 g of CO₂ per visit
4.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.32 g of CO₂e: 517.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
31 images without alt text
31 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
23 links without text
23 visible links have no text or label, so screen readers cannot say where they go.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
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
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.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
156 internal links, 21 external
The homepage links to 156 pages on izocam.com.tr and 21 external pages.
7 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Sunduğu kaliteli yalıtım ürünleri ile yalıtım sektörünün en önemli ismi olan İzocam enerji tasarrufu sağlayarak çevreni…”.
One H1 headline
Your main headline reads: “Ürünlerimiz”.
Title: 55 characters
Your title is a healthy 55 characters: “İzocam - Türkiye Yalıtım Sektöründe 1965'den Beri Lider”.
Canonical URL set
The canonical URL is https://www.izocam.com.tr/.
Structured data in place
Structured data found: BreadcrumbList and Organization.
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.izocam.com.tr/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.izocam.com.tr/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.
3 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 (672 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.izocam.com.tr/tr/kurumsal has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages slow to respond
https://www.izocam.com.tr/tr/urun-grubu/camyunu, https://www.izocam.com.tr/tr/urun-grubu/tasyunu and https://www.izocam.com.tr/tr/urun-grubu/ekstrude-polistiren-(xps) took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.
6 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.
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 15 pages that loaded have a <title>.
Best practices
45 small tap targets
45 of 92 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 “Cannot read properties of null (reading 'parentNode')”.
1 checks passed
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.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 663 words of copy
The homepage carries about 663 words of visible text.
4 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
18 other companies contacted
Loading the homepage contacts 18 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 izocam.com.tr, 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 | Google Tag Manager
- Hosting
- Azure
Company
- Founded
- 1965
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on izocam.com.tr, including 23 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.