Content - https://birsayt.az BeaverCheck Audit

F

Image Optimization

Action

7 issues found across 49 images

FIX

7 issues found across 49 images

5 images significantly larger than display size

Resizing to display dimensions could save approximately 2561 KB.

Got: ~2561 KB wasted

5 images missing explicit width/height

Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.

18 below-fold images missing loading="lazy"

Lazy loading defers below-fold images, reducing initial page weight.

All 49 images use legacy formats (JPEG/PNG/GIF)

WebP offers 25-35% smaller files than JPEG. Use <picture> with <source type="image/webp"> for modern format support.

Total image weight: 2706 KB (2.6 MB)

Consider compressing images, using modern formats, and serving appropriately sized images.

2 image(s) wider than 400px without srcset (no responsive serving)

These images deliver the same asset to every viewport (mobile, tablet, retina). Adding srcset / <picture> lets the browser pick a viewport-appropriate variant and typically saves 40-70% of bytes on mobile. Sample: https://static.wixstatic.com/media/cd0898_51a3ca303f5940e28c967bdf5859c8c7~mv2.jpg/v1/fill/w_980,h_509,al_c,q_85,usm_0.66_1.00_0.01,enc_avif,quality_auto/cd0898_51a3ca303f5940e28c967bdf5859c8c7~mv2.jpg, https://static.wixstatic.com/media/cd0898_371f65367dcd4d9facca8f7e45f0a02b~mv2.jpg/v1/fill/w_92,h_56,al_c,q_80,usm_0.66_1.00_0.01,blur_2,enc_avif,quality_auto/cd0898_371f65367dcd4d9facca8f7e45f0a02b~mv2.jpg.

1 image(s) rendered at a different aspect ratio than the source

The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://static.wixstatic.com/media/cd0898_371f65367dcd4d9facca8f7e45f0a02b~mv2.jpg/v1/fill/w_92,h_56,al_c,q_80,usm_0.66_1.00_0.01,blur_2,enc_avif,quality_auto/cd0898_371f65367dcd4d9facca8f7e45f0a02b~mv2.jpg.

B

Structured Data

1 JSON-LD block(s) found — some improvements recommended.

REVIEW

1 JSON-LD block(s) found — some improvements recommended.

Missing or invalid @context in block #1

The @context should be "https://schema.org" for search engines to recognize the data.

Got: https://schema.org/ Expected: https://schema.org

Missing recommended property "description" for WebSite

Adding "description" can improve how search engines display your content.

Missing recommended property "potentialAction" for WebSite

Adding "potentialAction" can improve how search engines display your content.

URL: https://schema.org/

The @context should be "https://schema.org" for search engines to recognize the data.

Expected: https://schema.org

Why this matters

JSON-LD without @context is invalid structured data — Google ignores the entire block.

Learn more ▾

@context must be 'https://schema.org' (or the schema-specific URL). Without it, the block isn't parseable as schema.org JSON-LD and Google skips it. Most schema generators handle this; manual edits sometimes drop the field.

Source: JSON-LD spec / schema.org

Adding "description" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

Adding "potentialAction" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

JSON-LD Blocks

Block 1 : WebSite

4 properties Valid

Missing or invalid @context

{
  "@context": "https://schema.org/",
  "@type": "WebSite",
  "name": "Birsayt.az",
  "url": "https://www.birsayt.az"
}

C

Brand Presence

Action

Site-name consistency, favicon, social image, meta tags, schema, and contact signals

REVIEW

Brand Presence

Your brand name differs across channels — visitors see inconsistent identity.

C

67/100

Site name appears as

Page title	Bakı
og:site_name	Birsayt.az
twitter:site	—
Organization.name	—

Inconsistent — names differ across channels

Brand assets

Favicon

12/15

covers apple-touch-icon

Social share image

20/20

og:image + twitter:image set

Meta completeness

20/20

Organization schema

0/15

Contact info discoverable

10/10

contact page, mailto link + tel link

Findings

Brand name differs across channels — users see inconsistent identity
Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
No Organization schema — Google can't render your logo in the knowledge panel

How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.

A+

Links

109 links checked, 109 healthy, 0 broken

PASS

109 links checked, 109 healthy, 0 broken

109 of 109 links are healthy

109 total 109 healthy

Broken Links (13)

Status	URL	Found in	Error
403	https://www.birsayt.az	`<link>`	Forbidden
403	https://www.birsayt.az/	`<link>`	Forbidden
403	https://www.birsayt.az/en	`<link>`	Forbidden
403	https://www.birsayt.az/ru	`<link>`	Forbidden
403	https://www.birsayt.az/tr	`<link>`	Forbidden
403	https://www.birsayt.az/blog-feed.xml	`<link>`	Forbidden
403	https://www.birsayt.az/haqq%C4%B1m%C4%B1zda	`<a>`	Forbidden
403	https://www.birsayt.az/referanslar	`<a>`	Forbidden
403	https://www.birsayt.az/services	`<a>`	Forbidden
403	https://www.birsayt.az/portfolio-vebsayt	`<a>`	Forbidden
403	https://www.birsayt.az/blog	`<a>`	Forbidden
403	https://www.birsayt.az/contact	`<a>`	Forbidden
403	https://www.birsayt.az/sale	`<a>`	Forbidden

200 https://static.wixstatic.com/media/cd0898_e9bbd9e5327843efbf... <link>

200 https://browser.sentry-cdn.com/7.120.3/bundle.tracing.es5.mi... <script>

200 https://connect.facebook.net/signals/config/4558333540952347... <script>

200 https://connect.facebook.net/en_US/fbevents.js <script>

200 https://www.googletagmanager.com/gtm.js?id=GTM-THVDF2G <script>

200 https://static.parastorage.com/unpkg/core-js-bundle@3.2.1/mi... <script>

200 https://static.parastorage.com/unpkg/focus-within-polyfill@5... <script>

200 https://static.parastorage.com/services/editor-elements-libr... <script>

200 https://photouploadwix.inspon-cloud.com/snowapp-api/script.j... <script>

200 https://cf06bdf3-5bab-4f20-b165-97fb723dac6a.wixappcloud.com... <script>

200 https://cf06bdf3-5bab-4f20-b165-97fb723dac6a.wixappcloud.com... <link>

200 https://www.googletagmanager.com/gtag/js?id=G-2EHTCSH5XR <script>

200 https://static.parastorage.com/services/cookie-consent-banne... <script>

200 https://static.parastorage.com/services/editor-elements-libr... <script>

200 https://static.wixstatic.com/media/cd0898_ae9cb0004d4241f3bd... <img>

200 https://static.parastorage.com/services/linguist-flags/1.100... <img>

200 https://api.whatsapp.com/send?phone=994553979099 <a>

A+

Mixed Content

No mixed content detected — all resources use HTTPS.

PASS

No mixed content detected — all resources use HTTPS.

No mixed content detected — all resources use HTTPS

A+

Open Graph

Open Graph tags are well configured for social sharing.

PASS

Open Graph tags are well configured for social sharing.

og:description is long (292 characters)

Descriptions over 200 characters may be truncated in social sharing previews.

Got: 292 chars Expected: 55–200 chars

URL: 292 chars

Descriptions over 200 characters may be truncated in social sharing previews.

Expected: 55–200 chars

Why this matters

og:description borderline-too-long — social platforms truncate around ~200 chars.

Source: Open Graph Protocol

Preview

birsayt.az

Veb Saytlarin Hazirlanmasi | Birsayt.az | Bakı

Veb saytlarin hazirlanmasi,Veb saytların hazırlanması,web saytlarin hazirlanmasi,veb sayt Birsayt qısa müddət ərzində istəyinizə uyğun veb saytı ən son texnologiyalardan istifadə ədərək qısa müddət ərzində hazırlayacayıq.! Birsayt.az web sayt saytlarin hazirlanmasi veb saytlarin hazirlanmasi

Preview quality · Twitter/X A+ · 95/100

Description will be truncated (316 chars / 200 max)

twitter:card — summary_large_image
twitter:title — Veb Saytlarin Hazirlanmasi | Birsayt.az | Bakı
twitter:description — Veb saytlarin hazirlanmasi,Veb saytların hazırlanması,web saytlarin hazirlanmasi,veb sayt Birsayt qısa müddət ərzində...
twitter:image — https://static.wixstatic.com/media/cd0898_922b2219c7dd4511a408b86931a0b887%7Emv2.png/v1/fit/w_2500,h_1330,al_c/cd0898...

Description will be truncated on Twitter/X (316 chars, max 200)
→ Tighten the description to ≤200 characters

BIRSAYT.AZ

Veb Saytlarin Hazirlanmasi | Birsayt.az | Bakı

Veb saytlarin hazirlanmasi,Veb saytların hazırlanması,web saytlarin hazirlanmasi,veb sayt Birsayt qısa müddət ərzində istəyinizə uyğun veb saytı ən son texnologiyalardan istifadə ədərək qısa müddət ərzində hazırlayacayıq.! Birsayt.az web sayt saytlarin hazirlanmasi veb saytlarin hazirlanmasi

Preview quality · Facebook A+ · 95/100

Description will be truncated (316 chars / 155 max)

og:title — Veb Saytlarin Hazirlanmasi | Birsayt.az | Bakı
og:description — Veb saytlarin hazirlanmasi,Veb saytların hazırlanması,web saytlarin hazirlanmasi,veb sayt Birsayt qısa müddət ərzində...
og:image — https://static.wixstatic.com/media/cd0898_922b2219c7dd4511a408b86931a0b887%7Emv2.png/v1/fit/w_2500,h_1330,al_c/cd0898...
og:type — website
og:url — https://www.birsayt.az
og:site_name — Birsayt.az

Description will be truncated on Facebook (316 chars, max 155)
→ Tighten og:description to ≤155 characters

Veb Saytlarin Hazirlanmasi | Birsayt.az | Bakı

birsayt.az

Preview quality · LinkedIn A+ · 95/100

Description will be truncated (316 chars / 150 max)

og:title — Veb Saytlarin Hazirlanmasi | Birsayt.az | Bakı
og:description — Veb saytlarin hazirlanmasi,Veb saytların hazırlanması,web saytlarin hazirlanmasi,veb sayt Birsayt qısa müddət ərzində...
og:image — https://static.wixstatic.com/media/cd0898_922b2219c7dd4511a408b86931a0b887%7Emv2.png/v1/fit/w_2500,h_1330,al_c/cd0898...

Description will be truncated on LinkedIn (316 chars, max 150)
→ Tighten og:description to ≤150 characters

birsayt.az

Veb Saytlarin Hazirlanmasi | Birsayt.az | Bakı

Veb saytlarin hazirlanmasi,Veb saytların hazırlanması,web saytlarin hazirlanmasi,veb sayt Birsayt qısa müddət ərzində istəyinizə uyğun veb saytı ən son texnologiyalardan istifadə ədərək qısa müddət ərzində hazırlayacayıq.! Birsayt.az web sayt saytlarin hazirlanmasi veb saytlarin hazirlanmasi

Preview quality · Slack A+ · 100/100

Description will be truncated (316 chars / 300 max)

og:title — Veb Saytlarin Hazirlanmasi | Birsayt.az | Bakı
og:description — Veb saytlarin hazirlanmasi,Veb saytların hazırlanması,web saytlarin hazirlanmasi,veb sayt Birsayt qısa müddət ərzində...
og:image — https://static.wixstatic.com/media/cd0898_922b2219c7dd4511a408b86931a0b887%7Emv2.png/v1/fit/w_2500,h_1330,al_c/cd0898...

Long description may be shortened by Slack (316 chars, guideline ~300)
→ Consider tightening to ~300 chars for the cleanest unfurl

Social preview quality

Averaged across Twitter/X, Facebook, LinkedIn, and Slack.

A+ · 96/100

Field	Facebook	LinkedIn	Slack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card	—	—	—
twitter:title	—	—	—
twitter:description	—	—	—
twitter:image	—	—	—

A+

Open Graph / Twitter Card Depth

OG image dimensions and Twitter card configuration look healthy

PASS

OG image dimensions and Twitter card configuration look healthy

OG/Twitter Card depth is clean -- dimensions, card type, and inheritance all valid

A+

Rich Results Eligibility

1 JSON-LD block(s) declaring 1 schema type(s)

PASS

1 JSON-LD block(s) declaring 1 schema type(s)

1 rich-result schema type(s) declared

Inventory of structured-data types on the page (each may unlock a different SERP feature): WebSite Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.

A+

Autoplay Media

No autoplay media on the page

PASS

No autoplay media on the page