40K Gallery is my own site, a curated archive of Warhammer 40,000 fan art and official artwork, with 16,756 artworks from 1,986 artists plus 4,974 pieces of official art, every one credited and linked back to the artist. I built it, I host it, and I run it, and it is by far the largest site I operate. It is also the site where I test everything before it goes near a client, because 100,000 people a month will find the problems a staging site never does.
By the numbers, over the last year the site has drawn over half a million visits from Google search and Google Images, 60 million search impressions in eight months, about 1.2 million page views a month with visitors averaging eight and a half pages per visit, 886 referring domains, and 1,700 keywords ranking in Google’s top three. It is cited by AI assistants too: Ahrefs tracks about 4,200 prompts across ChatGPT, Google AI Mode, Perplexity and Copilot that reference the site, and 3,300 Google AI Overviews that pull from 538 of its pages.
The site runs on WordPress with a custom child theme and a set of custom plugins I wrote for it, on the same hosting I use for client sites. Nothing on the site is scraped or pulled in automatically. Every artwork is hand selected by me, credited to the artist and linked back to them, then catalogued with artist, faction, character and style data so that the tag and category archives, which are where most of the search traffic lands, each have real descriptions and structure instead of being a bare list. That is slower than a bot, and it is why the site has artists sending in work rather than asking for it to be taken down. I built an Advanced Search that filters across all of it, a downloads section, and an affiliate system that places Amazon Associates banners and tracks clicks through the WordPress REST API into GA4, so I can see what works without a third party ad network slowing the pages down.
Performance on an image site is its own problem. The images are served through Cloudflare’s CDN with Polish handling WebP conversion at the edge, which let me remove over 27,000 redundant WebP files that a plugin had generated on the server. The result is 18,000 indexed pages passing Core Web Vitals on desktop with bounce rates under 10 percent on the main archive pages. I rebuilt the child theme’s functions.php from the ground up to clear out N+1 database queries and tighten the code, and that cleanup alone took a noticeable amount of load off the server.
A site full of artwork gets hit constantly by scrapers, hotlinkers and AI crawlers, so the site is targeted more often than any client site I manage. I won’t list the specifics, but in general terms: DNS and the edge run through Cloudflare, with the firewall, bot management and rate limiting configured to challenge automated traffic before it reaches WordPress; hotlink protection stops other sites from embedding the images directly; robots directives and crawler rules tell the AI scrapers that will listen to stay out, and the firewall deals with the ones that won’t; and the site publishes clear Image Usage Terms so the artists’ rights are stated up front. Behind that, the WordPress install is hardened and monitored, with the kind of security review I now do for client sites.
Everything I do for clients, I did here first: hosting, DNS, CDN, performance, security, SEO and custom development, on a site with real traffic.



