jobanalytics.com.tr website review

22 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.

About 459 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

75 files are served with short cache lifetimes, so returning visitors download them again (331 KiB).

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).

About 96 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

7 third-party services load with your homepage (Google Tag Manager, Google Analytics and Unpkg and others), adding 1.0 MB and 335 ms of main-thread time.

Google Tag Manager costs a phone 300 ms of main-thread work and 487 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.

Google Fonts costs a phone 1 ms of main-thread work and 332 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.

4 long tasks block the main thread while loading, the longest for 139 ms. During a long task the page ignores taps.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The layout shifts by 0.758 while loading, so content jumps under the reader's thumb. Good is under 0.1.

The page becomes fully interactive after 12.1 s. Good is under 3.8 s.

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

The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

5 images have no width and height attributes, so the layout jumps as each one loads.

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.

2 images (180 KiB) 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.

1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

7 tap targets are too small or too close together to hit reliably with a finger.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

1 element hidden from screen readers can still receive keyboard focus.

3 images have no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

32 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 176 characters, so Google will cut it off around 60: “JobAnalytics Adil Ücret Sistemi • İş Değerleme, Ücret Simülasyonu, Ücret Yönetimi, İnsan …”.

Structured data found ((untyped), ImageObject, Organization and Person) but with 1 problem, for example “block has no @type”.

1 link has no real href, so search engines can't follow it.

The homepage links to 70 pages on jobanalytics.com.tr and 13 external pages.

There is no https://www.jobanalytics.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.

https://www.jobanalytics.com.tr/en/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.jobanalytics.com.tr/jobanalytics-adil-ucret-sistemi-4 all use the title “JobAnalytics Adil Ücret Sistemi • İş Değerleme, Ücret Simülasyonu, Üc…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.jobanalytics.com.tr/cozumler, https://www.jobanalytics.com.tr/videolar, https://www.jobanalytics.com.tr/job-analytics-academy, https://www.jobanalytics.com.tr/blog, https://www.jobanalytics.com.tr/iletisim and https://www.jobanalytics.com.tr/demo-talep-edin have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jobanalytics.com.tr/jobanalytics-adil-ucret-sistemi-4, https://www.jobanalytics.com.tr/videolar, https://www.jobanalytics.com.tr/blog, https://www.jobanalytics.com.tr/iletisim, https://www.jobanalytics.com.tr/en/home and https://www.jobanalytics.com.tr/demo-talep-edin have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.jobanalytics.com.tr/iletisim has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.jobanalytics.com.tr/yapay-zeka-destekli-ucret-yapisi-nasil-kurulur took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 images are served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 486 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, 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.

Opening the homepage sets 7 cookies (measured from a US location before any click).

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.

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