Website review, no card needed

gema.org logo

gema.org website review

Visit site (opens in a new tab)Reviewed 23 October 202640 issues · 80 checks

This review found 40 issues worth fixing on gema.org, 13 of them high impact, across 80 checks. The most urgent: improve image delivery. 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

Full-page screenshot of gema.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix62
  • Improve image delivery

    6.7 s · 7.7 MB

    26 images could be 7.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.7 s faster on a phone.

  • Reduce unused JavaScript

    2.1 s · 471 KiB

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

  • Use efficient cache lifetimes

    1.2 s · 266 KiB

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

  • Render-blocking requests

    1.1 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.1 s.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Google Tag Manager and website-files.com and others), adding 10.2 MB and 623 ms of main-thread time.

  • website-files.com adds 112 ms

    112 ms

    website-files.com costs a phone 112 ms of main-thread work and 9.3 MB 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.

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62 (desktop: 59). Pages that score under 90 lose visitors before the first paint.

  • 2,746 HTML elements

    The page has 2,746 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Main-thread work: 2.4 s

    A phone's processor spends 2.4 s on main-thread work while loading, 807 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused CSS

    150 ms · 67 KiB

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

  • 8 long tasks on the main thread

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

  • Duplicated JavaScript

    44 KiB

    44 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

  • 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.

  • Forced reflow

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

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix60
  • Largest Contentful Paint: 23.0 s

    23.0 s

    Your largest element takes 23.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to analyze our traffic. By clicking “Accept …”.

  • Time to Interactive: 23.1 s

    23.1 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • 100 images without width and height

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

  • Total Blocking Time: 274 ms

    274 ms

    Scripts block taps and scrolling for 274 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix25
  • Page weight: 11.7 MB in 130 requests

    11.7 MB

    Your homepage downloads 11.7 MB in 130 requests on a phone: images 8.2 MB (63), media 1.2 MB (2) and scripts 1.2 MB (49). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 7.6 MB together. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    4.6 MB

    5 images are downloaded at several times the size a phone draws them, for example 6aa9b41ba33cebfa4c463557_DEC.10_Website_Banner_RD1.png at 2,200 px wide, shown at 368 px. Resized copies would save about 4.6 MB.

  • 5 images in older formats

    5 images (7.6 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.

  • 2 images below the first screen load straight away

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

  • About 3.3 g of CO₂ per visit

    3.31 g

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

Accessibility

5 to fixGoogle 9494
  • All page content should be contained by landmarks (26 elements)

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

  • No main landmark

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

  • Page should contain a level-one heading (1 element)

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

  • 10 links without text

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

  • 1 form field without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 194 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 9280
  • No H1 headline

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (375 characters)

    Your meta description is 375 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 57 internal links, 24 external

    The homepage links to 57 pages on gema.org and 24 external pages.

5 checks passed
  • Title: 61 characters

    Your title is a healthy 61 characters: “THE GLOBAL ENTERTAINMENT MARKETING ACADEMY OF ARTS & SCIENCES”.

  • Canonical URL set

    The canonical URL is https://www.gema.org/.

  • 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://gema.org/sitemap.xml.

AI search readiness

2 to fix75
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • Some text only appears after JavaScript runs

    56%

    The HTML your server sends has 336 of the 595 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://gema.org/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.

1 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.

Other pages

6 to fix52
  • 2 linked pages are broken

    Your homepage links to https://gema.org/events and https://gema.org/subscribe-old, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 linked page hidden from search

    https://gema.org/privacy-policy is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://gema.org/membership-portal, https://gema.org/calendar and https://gema.org/subscribe have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://gema.org/membership and https://gema.org/partnership use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://gema.org/membership-portal, whose canonical is https://gema.org/member-login. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 10 pages without an H1

    https://gema.org/membership-portal, https://gema.org/awards, https://gema.org/news, https://gema.org/story-sparks, https://gema.org/partnership and https://gema.org/about and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://gema.org/subscribe 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.

  • 15 internal pages checked

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

2 checks passed
  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9676
  • 4 broken images

    4 images failed to load on a phone, for example https://cdn.prod.website-files.com/659c07a933001f794b2f07b3/698bc8fe025a606f6582a9ed_70th_GEMA_Black-p-500.png.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_CLOSED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 595 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REGISTER NOW” and “REGISTER HERE”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “ORDER STATUES”, “why join” and “apply now”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 180 customer or partner logos and 4 trust badges.

  • Analytics in place

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

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

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

  • 14 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 gema.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google 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 40 issues on gema.org, including 15 speed issues, 4 SEO issues and 1 conversion gap. 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
gema.org website review: scores and fixes | Programmable