Website review, no card needed

adresgezgini.com logo

adresgezgini.com website review

Visit site (opens in a new tab)Reviewed 22 October 202618 issues · 76 checks

This review found 18 issues worth fixing on adresgezgini.com, 7 of them high impact, across 76 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Real-visitor load time (LCP)75th percentile, phones
3.3 s1.1 sMay 2Oct 172.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.4 s
May 9, 20262.3 s
May 16, 20262.6 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20263.0 s
Aug 15, 20262.9 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20262.8 s
Sep 12, 20262.9 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Oct 17, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
297 ms87 msMay 2Oct 17194 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026193 ms
May 9, 2026203 ms
May 16, 2026203 ms
May 23, 2026221 ms
May 30, 2026243 ms
Jun 6, 2026253 ms
Jun 13, 2026273 ms
Jun 20, 2026238 ms
Jun 27, 2026202 ms
Jul 4, 2026181 ms
Jul 11, 2026153 ms
Jul 18, 2026134 ms
Jul 25, 2026119 ms
Aug 1, 2026111 ms
Aug 8, 2026113 ms
Aug 15, 2026120 ms
Aug 22, 2026144 ms
Aug 29, 2026153 ms
Sep 5, 2026159 ms
Sep 12, 2026167 ms
Sep 19, 2026146 ms
Sep 26, 2026160 ms
Oct 3, 2026147 ms
Oct 10, 2026164 ms
Oct 17, 2026194 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

Full-page screenshot of adresgezgini.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

95
  • Improve image delivery

    102 KiB

    2 images could be 102 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Cloudflare CDN and Bootstrap CDN), adding 64 KiB and 49 ms of main-thread time.

  • Reduce unused CSS

    25 KiB

    About 25 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    12 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (12 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.

3 checks passed
  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95 (desktop: 99). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 164 ms of it running JavaScript. That is comfortably low.

  • Server response: 176 ms

    176 ms

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

Core Web Vitals

6 to fix67
  • 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 TTFB: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Real-user LCP: 2.9 s

    2.9 s

    Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Largest content (LCP) got 62% slower for real visitors

    +62%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.9 s

    2.9 s

    Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

  • Speed Index: 4.0 s

    4.0 s

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

8 checks passed
  • Real-user INP: 191 ms

    191 ms

    Real visitors wait 191 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 10% faster for real visitors

    -10%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 193 ms to 194 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.081

    0.081

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

  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Size daha iyi ve kurumsal bir hizmet verebilmek için firmam…”.

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Time to Interactive: 2.2 s

    2.2 s

    The page is fully interactive after 2.2 s.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix80
  • 3 images far larger than shown

    549 KiB

    3 images are downloaded at several times the size a phone draws them, for example cookie.png at 2,172 px wide, shown at 115 px. Resized copies would save about 549 KiB.

  • 1 image in older formats

    1 image (470 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.

  • 3 images below the first screen load straight away

    3 images further down the page (209 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.1 g of CO₂ per visit

    0.14 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.14 g of CO₂e: 16.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Page weight: 492 KiB in 26 requests

    492 KiB

    Your homepage downloads 492 KiB in 26 requests on a phone: images 278 KiB (11), fonts 90 KiB (6) and scripts 68 KiB (5). That is a lean page.

Accessibility

2 to fixGoogle 9697
  • 5 text elements with low contrast

    5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 147 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 6 links crawlers can't follow

    6 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 set, so this is minor.

  • 86 internal links, 20 external

    The homepage links to 86 pages on adresgezgini.com and 20 external pages.

8 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “AdresGezgini, Google Ads Reklam, Facebook Reklam, Sponsor Bağlantı Reklam Yönetimi ve Kurumsal Çözümler, Profesyonel De…”.

  • One H1 headline

    Your main headline reads: “GOOGLE ADS PREMIER PARTNER”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “AdresGezgini | Google Ads Reklam Premier Partner 444 0 964”.

  • Canonical URL set

    The canonical URL is https://adresgezgini.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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://adresgezgini.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (681 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://adresgezgini.com/llms.txt (5 KiB, 34 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 3 pages share a title

    /, https://adresgezgini.com/en and https://adresgezgini.com/hizmetlerimiz/kampanyalar all use the title “AdresGezgini | Google Ads Reklam Premier Partner 444 0 964”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages share a meta description

    https://adresgezgini.com/en, https://adresgezgini.com/hakkimizda/medya-kiti, https://adresgezgini.com/hakkimizda/akademik-yayinlarimiz and https://adresgezgini.com/hizmetlerimiz/kampanyalar use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 61 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.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://adresgezgini.com/themes/2018/images/x-logo.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    34 of 41 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 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 609 words of copy

    The homepage carries about 609 words of visible text.

4 checks passed
  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 adresgezgini.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
jQuery
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on adresgezgini.com, including 6 speed issues, 1 SEO issue 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