ravensoftware.com website review

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

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

113 files are served with short cache lifetimes, so returning visitors download them again (18.6 MB).

15 images could be 10.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Optanon and others), adding 62.0 MB and 772 ms of main-thread time.

activision.com costs a phone 0 ms of main-thread work and 61.4 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.

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

About 209 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

Google CDN costs a phone 378 ms of main-thread work and 31 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.

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

37 KiB could be saved by minifying JavaScript.

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

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

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

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

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 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OUR WORK SPEAKS FOR US”.

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

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

Real visitors wait 217 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

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

Your homepage downloads 77.3 MB in 134 requests on a phone: media 63.4 MB (6), images 13.0 MB (80) and scripts 637 KiB (17). Under 2 MB keeps phones on slow connections fast.

3 images weigh 11.3 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example laura-tab-image.jpg at 6,192 px wide, shown at 392 px. Resized copies would save about 9.7 MB.

12 images further down the page (11.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (953 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 21.90 g of CO₂e: 2627.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Some list items are not inside a list.

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

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

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

Headings skip levels (h2 → 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 only 14 characters: “Raven Software”. Between 30 and 65 characters leaves room to say what you do and for whom.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No XML sitemap at https://www.ravensoftware.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at ravensoftware.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 14 pages on ravensoftware.com and 34 external pages.

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.

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

/ and https://www.ravensoftware.com/home all use the title “Raven Software”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ravensoftware.com/our-games, https://www.ravensoftware.com/social-impact, https://www.ravensoftware.com/blog/2026/02/call-of-duty-mobile-season-2-lunar-charge and https://www.ravensoftware.com/blog/2026/02/call-of-duty-black-ops-7-warzone-battle-pass-blackcell-store-season-02 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ravensoftware.com/home, https://www.ravensoftware.com/blog/2026/02/call-of-duty-mobile-season-2-lunar-charge and https://www.ravensoftware.com/blog/2026/02/call-of-duty-black-ops-7-warzone-battle-pass-blackcell-store-season-02 have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ravensoftware.com/blog/2026/02/call-of-duty-mobile-season-2-lunar-charge and https://www.ravensoftware.com/blog/2026/02/call-of-duty-black-ops-7-warzone-battle-pass-blackcell-store-season-02 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.

We fetched 5 pages linked from your homepage and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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 519 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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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