olympic.sa website review

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

The HTML itself could arrive about 850 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

Reduce initial server response time. Google estimates savings of 858 ms on a phone.

2 images could be 306 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

Your server takes 958 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

2 third-party services load with your homepage (Google Fonts and Cloudflare CDN), adding 328 KiB and 1 ms of main-thread time.

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

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.

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

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

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

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

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

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

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

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

1 image is downloaded at several times the size a phone draws it, for example participants-logo.png at 1,200 px wide, shown at 120 px. Resized copies would save about 268 KiB.

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

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

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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

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

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 45 pages on olympic.sa and 43 external pages.

There is no https://olympic.sa/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://olympic.sa/about-us, https://olympic.sa/blog, https://olympic.sa/our-history, https://olympic.sa/our-champions, https://olympic.sa/team-saudi and https://olympic.sa/games and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://olympic.sa/about-us, https://olympic.sa/blog, https://olympic.sa/our-history, https://olympic.sa/our-champions, https://olympic.sa/team-saudi and https://olympic.sa/games and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://olympic.sa/games, https://olympic.sa/contact-us and https://olympic.sa/ar have 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://olympic.sa/our-history, https://olympic.sa/our-champions, https://olympic.sa/team-saudi, https://olympic.sa/games, https://olympic.sa/gallery and https://olympic.sa/contact-us and 1 other took over 3 s to send their HTML from our server.

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

12 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

Social proof on the homepage: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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 256 words of visible text.

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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.