Catalog / meydane.org
39

SEO audit for meydane.org

Institut Meydane

other

Health 39/100 (poor) · 50 pages crawled · generated 2026-08-26

Download Markdown report (feed to ChatGPT / Claude / Cursor)

INSTITUT MEYDANE

Screenshot of meydane.org
50
pages crawled
48
indexable pages
22
errors
198
warnings
277
notices
0
orphan pages
2
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Security 64 18 0 66
Links 95 2 2 0
Crawlability 96 2 0 2
Structured Data 42 0 96 0
Performance 77 0 39 94
Meta Description 78 0 36 11
Content 92 0 14 0
Duplicate 96 0 7 3
Images 99 0 2 15
Budget 99 0 1 0
Canonical 99 0 1 20
Agent Readiness 100 0 0 11
Headings 100 0 0 7
Social 100 0 0 45
Titles 100 0 0 2
URL 100 0 0 1
Findings

Errors (3 rules)

error Broken internal link (target 4xx/5xx)

Rule links.broken_internal · Links · 2 occurrence(s)

error Mixed content on HTTPS page

Rule security.mixed_content · Security · 18 occurrence(s)

error Client error (4xx) response

Rule status.4xx · Crawlability · 2 occurrence(s)

Warnings (13 rules)

warning robots.txt-disallowed URL receives internal links (crawl-budget leak)

Rule budget.disallow_linked · Budget · 1 occurrence(s)

  • http://www.meydane.org/search — internal links point to http://www.meydane.org/search, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: http://www.meydane.org/Amir%20Mohse, http://www.meydane.org/take-action.

warning Interior page canonicalizes to the homepage

Rule canonical.points_to_homepage · Canonical · 1 occurrence(s)

  • http://www.meydane.org/home — this interior page canonicalizes to the homepage (http://www.meydane.org/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.

warning Thin content (low word count)

Rule content.thin · Content · 14 occurrence(s)

warning Duplicate page content

Rule duplicate.content · Duplicate · 2 occurrence(s)

warning Homepage duplicated across protocol/host variants (no redirect)

Rule duplicate.protocol_host · Duplicate · 1 occurrence(s)

  • https://www.meydane.org/ — http://www.meydane.org/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.

warning Duplicate <title> across pages

Rule duplicate.title · Duplicate · 4 occurrence(s)

warning Images missing alt text

Rule images.missing_alt · Images · 2 occurrence(s)

warning Hero/LCP image is lazy-loaded (loading=lazy delays LCP)

Rule images.no_lazy_lcp_candidate · Performance · 36 occurrence(s)

  • http://www.meydane.org/073614145539 — the likely hero/LCP image (17.01.15.andalousie.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/2013 — the likely hero/LCP image (16.12.expo+photos.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/2014-1 — the likely hero/LCP image (05.03atelier+caligraphie.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/2015 — the likely hero/LCP image (12195082_1065532893464854_3322977331981482906_o.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/2017 — the likely hero/LCP image (25152246_1928409440510524_8612536373205775228_n.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/2017-1 — the likely hero/LCP image (23795786_1344278729017555_5819618336721799871_n.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/2018-event — the likely hero/LCP image (46889845_1923467997959487_5178725678362656768_n.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/2020 — the likely hero/LCP image (131026897_2441918736114408_3846506436286176136_o.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/2020-1 — the likely hero/LCP image (104415394_2300373540268929_3639382757178944984_n.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/2021-1 — the likely hero/LCP image (174107721_4096745880357516_3340402209718777202_n.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/conf2019 — the likely hero/LCP image (78546823_2147355405570744_4906869147767406592_n.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/confrences2018 — the likely hero/LCP image (47239975_356734345148320_1395901531257044992_n.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/events2016 — the likely hero/LCP image (image-asset.jpeg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/events2019 — the likely hero/LCP image (58694108_2197630960319241_8871094648823611392_n.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/events2021-norouz — the likely hero/LCP image (whatsapp+image+2021-03-10+at+20.14.48.jpeg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/home — the likely hero/LCP image (f129-khorsabad-1-taureau-profil.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/membership — the likely hero/LCP image (sepand-iphone%27s+pictures-nov+2015+1113.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/new-folder — the likely hero/LCP image (174107721_4096745880357516_3340402209718777202_n.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/new-page-4 — the likely hero/LCP image (image-asset.jpeg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/orient2020 — the likely hero/LCP image (41-facebook+cover.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • http://www.meydane.org/rient2020 — the likely hero/LCP image (41-facebook+cover.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.meydane.org/ — the likely hero/LCP image (f129-khorsabad-1-taureau-profil.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.meydane.org/2020-1 — the likely hero/LCP image (104415394_2300373540268929_3639382757178944984_n.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.meydane.org/2021-1 — the likely hero/LCP image (174107721_4096745880357516_3340402209718777202_n.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.meydane.org/conf2019 — the likely hero/LCP image (78546823_2147355405570744_4906869147767406592_n.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.

warning Internal link points to a redirect

Rule links.redirect_target · Links · 2 occurrence(s)

warning Missing meta description

Rule meta_desc.missing · Meta Description · 36 occurrence(s)

warning Render-blocking script in <head> (no defer/async)

Rule perf.render_blocking · Performance · 3 occurrence(s)

warning Rich-result schema missing required properties

Rule schema.invalid · Structured Data · 48 occurrence(s)

warning LocalBusiness schema missing required properties (name/address)

Rule schema.localbusiness_incomplete · Structured Data · 48 occurrence(s)

  • http://www.meydane.org/073614145539 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/2013 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/2014-1 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/2015 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/2017 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/2017-1 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/2018-event — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/a-venir — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/aboutus — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/conf2019 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/confrences2018 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/events — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/events2016 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/events2019 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/home — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/membership — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/new-folder — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/new-index — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/new-page-3 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/new-page-4 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/nos-principes-1 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/nouvelle-page — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/orient2020 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • http://www.meydane.org/rient2020 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • https://www.meydane.org/ — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.

Notices (21 rules)

notice Heading levels skip a level

Rule agent.heading_skip · Agent Readiness · 10 occurrence(s)

notice No llms.txt for AI agents

Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)

notice Canonical target reachable only via a canonical tag (no inlinks)

Rule canonical.isolated_url · Canonical · 1 occurrence(s)

  • http://www.meydane.org/new-folder — this URL is a canonical target but has no internal links pointing to it — crawlers only learn of it via the canonical tag. Add direct internal links (or list it in the sitemap).

notice Canonical points to a different URL

Rule canonical.non_self · Canonical · 19 occurrence(s)

notice Title tag and meta description are identical

Rule content.title_meta_same · Meta Description · 2 occurrence(s)

  • http://www.meydane.org/home — the meta description is identical to the <title> — write a distinct description to control the SERP snippet
  • https://www.meydane.org/ — the meta description is identical to the <title> — write a distinct description to control the SERP snippet

notice Duplicate meta description across pages

Rule duplicate.meta_desc · Duplicate · 3 occurrence(s)

notice Multiple <h1> elements

Rule h1.multiple · Headings · 7 occurrence(s)

notice Image alt text is keyword-stuffed (repetition / low variety)

Rule images.alt_stuffed · Images · 2 occurrence(s)

  • http://www.meydane.org/2017 — 2 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.
  • https://www.meydane.org/2017 — 2 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.

notice Image alt text is very long (possible keyword stuffing)

Rule images.alt_too_long · Images · 6 occurrence(s)

notice Likely hero image lacks fetchpriority=high

Rule images.hero_no_fetchpriority · Performance · 5 occurrence(s)

  • http://www.meydane.org/aboutus — the likely hero/LCP image (d59206939b675cdf3cc2a65239e9e74e.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.meydane.org/blog — the likely hero/LCP image (gettyimages-950006508-2048x2048.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.meydane.org/home-alt-bedford — the likely hero/LCP image (chambers-2.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.meydane.org/about — the likely hero/LCP image (d59206939b675cdf3cc2a65239e9e74e.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.meydane.org/aboutus — the likely hero/LCP image (d59206939b675cdf3cc2a65239e9e74e.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.

notice Images without width/height (layout shift / CLS)

Rule images.missing_dimensions · Images · 7 occurrence(s)

notice Meta description too long

Rule meta_desc.too_long · Meta Description · 1 occurrence(s)

notice Meta description too short

Rule meta_desc.too_short · Meta Description · 8 occurrence(s)

notice Missing Open Graph tags

Rule og.missing · Social · 45 occurrence(s)

notice Legacy image format (jpg/png/gif) with no next-gen fallback

Rule perf.images_legacy_format · Performance · 41 occurrence(s)

  • http://www.meydane.org/073614145539 — 6 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/2013 — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/2014-1 — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/2015 — 6 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/2017 — 14 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/2017-1 — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/2018-event — 12 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/2020 — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/2020-1 — 8 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/2021-1 — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/aboutus — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/blog — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/conf2019 — 10 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/confrences2018 — 7 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/events2016 — 16 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/events2019 — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/events2021-norouz — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/home — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/home-alt-bedford — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/membership — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/new-folder — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/new-page-4 — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/orient2020 — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.meydane.org/rient2020 — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.meydane.org/ — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.

notice No Last-Modified header (no conditional GET for unchanged pages)

Rule perf.no_last_modified · Performance · 48 occurrence(s)

  • http://www.meydane.org/073614145539 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/2013 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/2014-1 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/2015 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/2017 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/2017-1 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/2018-event — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/a-venir — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/aboutus — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/conf2019 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/confrences2018 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/events — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/events2016 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/events2019 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/home — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/membership — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/new-folder — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/new-index — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/new-page-3 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/new-page-4 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/nos-principes-1 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/nouvelle-page — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/orient2020 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • http://www.meydane.org/rient2020 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.meydane.org/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.

notice URL redirects to another URL

Rule redirect.single · Crawlability · 2 occurrence(s)

notice Missing recommended security headers

Rule security.missing_headers · Security · 18 occurrence(s)

notice target=_blank link without rel=noopener (tab-napping)

Rule security.unsafe_cross_origin_links · Security · 48 occurrence(s)

  • http://www.meydane.org/073614145539 — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/2013 — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/2014-1 — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/2015 — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/2017 — 7 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/2017-1 — 2 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/2018-event — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/a-venir — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/aboutus — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/conf2019 — 5 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/confrences2018 — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/events — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/events2016 — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/events2019 — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/home — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/membership — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/new-folder — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/new-index — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/new-page-3 — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/new-page-4 — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/nos-principes-1 — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/nouvelle-page — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/orient2020 — 3 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • http://www.meydane.org/rient2020 — 2 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.meydane.org/ — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".

notice Title tag is identical to the H1 (missed keyword variation)

Rule title.same_as_h1 · Titles · 2 occurrence(s)

notice Uppercase letters in URL path

Rule url.uppercase · URL · 1 occurrence(s)

Pages (showing 50 of 50)
URLStatusIndexableWordsIn-links
http://www.meydane.org/073614145539
Evènements Meydane 2015 — Institut Meydane		 200 yes 163 32
http://www.meydane.org/2013
2013 — Institut Meydane		 200 yes 96 32
http://www.meydane.org/2014-1
Evènements Meydane 2014 — Institut Meydane		 200 yes 133 32
http://www.meydane.org/2015
2015 — Institut Meydane		 200 yes 663 32
http://www.meydane.org/2017
2017 — Institut Meydane		 200 yes 2773 32
http://www.meydane.org/2017-1
2017 — Institut Meydane		 200 yes 437 32
http://www.meydane.org/2018-event
Evènements Meydane 2018 — Institut Meydane		 200 yes 1117 32
http://www.meydane.org/2020
Evènements Meydane 2020 — Institut Meydane		 200 yes 248 32
http://www.meydane.org/2020-1
2020 — Institut Meydane		 200 yes 4860 32
http://www.meydane.org/2021-1
2021 — Institut Meydane		 200 yes 1502 32
http://www.meydane.org/aboutus
Institut Meydane — Institut Meydane		 200 yes 339 32
http://www.meydane.org/blog
Blog — Institut Meydane		 200 yes 3068 32
http://www.meydane.org/conf2019
Conférences Meydane 2019 — Institut Meydane		 200 yes 2627 32
http://www.meydane.org/confrences2018
Conférences 2018 — Institut Meydane		 200 yes 2739 32
http://www.meydane.org/events2016
Evènements Meydane 2016 — Institut Meydane		 200 yes 251 32
http://www.meydane.org/events2019
Evènements Meydane 2019 — Institut Meydane		 200 yes 755 32
http://www.meydane.org/membership
Rejoignez-nous — Institut Meydane		 200 yes 114 32
http://www.meydane.org/new-page-4
2016 — Institut Meydane		 200 yes 686 32
http://www.meydane.org/nos-principes-1
NOS PRINCIPES — Institut Meydane		 200 yes 160 32
http://www.meydane.org/orient2020
Orient 2020, bilan et perspective — Institut Meydane		 200 yes 417 32
https://www.meydane.org/
Institut Meydane		 200 yes 590 18
https://www.meydane.org/073614145539
Evènements Meydane 2015 — Institut Meydane		 200 yes 163 18
https://www.meydane.org/2014-1
Evènements Meydane 2014 — Institut Meydane		 200 yes 133 18
https://www.meydane.org/2015
2015 — Institut Meydane		 200 yes 663 18
https://www.meydane.org/2017
2017 — Institut Meydane		 200 yes 2773 18
https://www.meydane.org/2017-1
2017 — Institut Meydane		 200 yes 437 18
https://www.meydane.org/2018-event
Evènements Meydane 2018 — Institut Meydane		 200 yes 1117 18
https://www.meydane.org/2020
Evènements Meydane 2020 — Institut Meydane		 200 yes 248 18
https://www.meydane.org/2020-1
2020 — Institut Meydane		 200 yes 4860 18
https://www.meydane.org/2021-1
2021 — Institut Meydane		 200 yes 1502 18
https://www.meydane.org/aboutus
Institut Meydane — Institut Meydane		 200 yes 339 18
https://www.meydane.org/conf2019
Conférences Meydane 2019 — Institut Meydane		 200 yes 2627 18
https://www.meydane.org/confrences2018
Conférences 2018 — Institut Meydane		 200 yes 2739 18
https://www.meydane.org/events2016
Evènements Meydane 2016 — Institut Meydane		 200 yes 251 18
https://www.meydane.org/events2019
Evènements Meydane 2019 — Institut Meydane		 200 yes 755 18
https://www.meydane.org/new-page-4
2016 — Institut Meydane		 200 yes 686 18
https://www.meydane.org/nos-principes-1
NOS PRINCIPES — Institut Meydane		 200 yes 160 18
https://www.meydane.org/about
Institut Meydane — Institut Meydane		 200 yes 339 2
http://www.meydane.org/a-venir
A VENIR — Institut Meydane		 200 yes 82 0
http://www.meydane.org/events
Events — Institut Meydane		 200 yes 82 0
http://www.meydane.org/events2021-norouz
Norouz Meydane 2021 — Institut Meydane		 200 yes 482 0
http://www.meydane.org/home
Institut Meydane		 200 yes 590 0
http://www.meydane.org/home-alt-bedford
Home Alt — Institut Meydane		 200 yes 120 0
http://www.meydane.org/new-folder
2021 — Institut Meydane		 200 yes 1502 0
http://www.meydane.org/new-index
Accueil — Institut Meydane		 200 yes 74 0
http://www.meydane.org/new-page-3
New Page — Institut Meydane		 200 yes 74 0
http://www.meydane.org/nouvelle-page
2019 — Institut Meydane		 200 yes 74 0
http://www.meydane.org/rient2020
Copy of Orient 2020 — Institut Meydane		 200 yes 377 0
http://www.meydane.org/Amir%20Mohse
Institut Meydane		 404 no 142 1
http://www.meydane.org/take-action
Institut Meydane		 404 no 142 1

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →