On three of the four faymas domains the pictures outweigh the words. We counted every image tag on 110 pages across faymas.in, faymas.net, faymas-in.com and faymas.com.in on 21 October 2026 — 1,613 tags pointing at 812 distinct files — and then fetched 84 of those files. One faymas.in prompt page pulls 1.68 MB of images behind 526 KB of HTML, 3.3× more image than text. One faymas.net gallery page pulls 1.88 MB behind 173 KB, 11×. The faymas-in.com homepage pulls 3.13 MB of distinct image files behind 66 KB of HTML, 49×, and its single largest file is a 2.36 MB PNG. The exception is faymas.com.in: 0.18 MB of images behind 214 KB of HTML, and three real image files on the entire site.
This guide analyses published prompt text. No generation tests were run.
What we measured
One script, one measure(), four domains, same morning. For each page it fetched the server HTML, collected every <img>, and resolved a real URL for each one: the src attribute if it is not a base64 placeholder, otherwise data-src, otherwise the first entry in srcset. That last rule matters more than it sounds. On faymas.com.in all ten image tags carry a base64 placeholder as their src; the real file only appears in data-src. Counting src alone would have reported "this site has no images", which is wrong in a different way than "this site has ten images".
Then we fetched the files themselves: 12–15 content images plus the chrome images on each of the three larger domains, and every image on one representative page per domain. We recorded status, content type, byte length, MD5, cache headers, and — by reading the file header — the real pixel dimensions.
The samples are shaped by what each domain has. faymas.in publishes a 20,323-URL sitemap; we took its homepage, 25 random prompt pages, 6 blog posts, 6 category pages, 4 collection pages and 4 static pages = 46. faymas.net declares 41 URLs and hides a set of /prompts/p/ pages its sitemap omits; we fetched all 41 declared plus 15 of the unlisted ones = 56. The two WordPress domains are small: faymas-in.com has 3 posts, faymas.com.in has 4 pages, and we took every one.
The weight: images against HTML
| Domain | Page measured | HTML | <img> tags | Distinct files | Image bytes (distinct) | Image bytes (every tag) | Ratio |
|---|---|---|---|---|---|---|---|
| faymas.in | /prompt/silent-leader-concept-e4db3427 | 526 KB | 14 | 14 | 1.68 MB | 1.68 MB | 3.3× |
| faymas.net | /prompts/p/lifestyle-black-and-white-young-woman-from-the-chest-up-portrait-8293129 | 173 KB | 13 | 12 | 1.88 MB | 1.95 MB | 11× |
| faymas-in.com | / (home) | 66 KB | 12 | 4 | 3.13 MB | 6.27 MB | 49× |
| faymas.com.in | / (home) | 214 KB | 4 | 3 | 0.18 MB | 0.18 MB | 0.9× |
Two rows deserve a closer look. faymas-in.com's homepage carries 12 image tags but only 4 distinct files: each featured image is emitted twice, once eagerly with a srcset and once as a lazy-loaded copy, so a browser that fetched every tag would download 6.27 MB. Three of those four files are photographs; the fourth is a 24×24 avatar, 1,144 bytes, requested six times.
faymas.com.in inverts the pattern the other three follow. Its HTML is heavier than all of its images put together, and its whole site rests on three files: Faymas-in.jpg (2,094 bytes, 150×150), Faymas-ai-prompt-1024x416.webp (86,050 bytes) and 2-1-1024x424.webp (98,786 bytes). A site about AI photo prompts, with no photographs on it.
Where the files live, and what they are called
| Domain | Hosts serving images | Formats | Naming |
|---|---|---|---|
| faymas.in | cdn.faymas.in 578, faymas.in 39 (icons) | webp 578, svg 27, no extension 12 | /prompt_outputs/<uuid>/<uuid>.webp — no words in the URL |
| faymas.net | 2 separate *.r2.dev buckets 752, www.faymas.net 202 | webp 453, jpg 333, png 131, avif 35, jpeg 1, svg 1 | /ai-prompts/portrait-photography-prompts/x/studio-cyberpunk-close-up-man-portrait-6965234.webp — readable |
| faymas-in.com | faymas-in.com 23, secure.gravatar.com 9 | webp 12, png 11 | WordPress original filenames |
| faymas.com.in | faymas.com.in 10 (3 distinct files) | jpg 8, webp 2 | Faymas-in.jpg, 2-1.webp |
The naming is where the four domains stop looking alike. faymas.in names its outputs after nothing — a UUID directory and a UUID filename, so the URL tells a crawler nothing about what is in the picture. faymas.net does the opposite: its image paths are readable slugs that repeat the page's own subject, which means its image URLs are themselves keyword-bearing text. Both approaches are defensible; they are just built by different people.
faymas.in.com's filenames are the most quotable thing in this dataset. One featured image is stored as ChatGPT-Image-Sep-23-2026-03_14_39-PM-1.webp13-Ganesh-Chaturthi-AI-Photo-Prompts-to-Create-Stunning-Ganpati-Bappa-Photos-1.webp. That is two filenames glued together with no separator: the first half is the default name a ChatGPT download produces, the second half is the post title. We are reporting what the filename says — we did not verify where the image came from — but the string is on the site's own server, in six size variants, and it tells you the "AI photo" examples were saved out of a chat window rather than generated into a pipeline.
faymas.net also splits its output images across two Cloudflare R2 buckets, pub-0413a9c78ce5…r2.dev and pub-ba45bd3ba59f…r2.dev, both on the raw r2.dev development hostname rather than a custom domain.
Are the pictures real?
Yes, on the three domains that have them. Every one of the 84 image requests we made returned HTTP 200. We hashed each body, and every sampled file was a different file: 15 of 15 distinct on faymas.in, 13 of 13 on faymas.net, 13 of 13 on faymas-in.com. No placeholder is standing in for a picture anywhere we looked. Median file size was about 140 KB on faymas.in and about 143 KB on faymas.net. Median aspect ratio was 0.75 on both — portrait, which is what you would expect from a prompt library aimed at phone wallpapers.
The reuse we did find happens one level up, at the tag level rather than the file level. faymas.net emits logo.png twice on every page it serves. faymas-in.com's homepage carries 12 image tags that resolve to 4 distinct files. No page is borrowing another page's photograph; some pages are asking for their own twice.
Cross-page reuse separates the two large domains cleanly. faymas.in used 438 distinct files across 617 tags, 1.41 uses per file, and 383 of those 438 files (87%) appear on exactly one page. Not one file appears on as many as half the pages we fetched. faymas.net used 362 distinct files across 954 tags, 2.63 uses per file, and one file appears on all 56 pages: logo.png, a 76 KB 512×512 PNG, emitted twice on every page, served with cache-control: public, max-age=0, must-revalidate. The one picture guaranteed to be on every faymas.net page is the one picture that is never allowed to be cached.
Caching is otherwise the strongest thing any of these sites does with images. faymas.in serves its outputs with public, max-age=31536000, immutable, and faymas.net's bucket files carry the same header; both are correct for files whose URLs change when content changes. faymas-in.com and faymas.com.in use public, max-age=604800, seven days, and faymas-in.com's avatars use max-age=300.
What the image layer gets wrong
| Domain | <img> tags | alt missing | alt empty | alt with text (median words) | loading="lazy" | width + height both set | og:image |
|---|---|---|---|---|---|---|---|
| faymas.in | 617 | 0 | 8 | 609 (11 words) | 438 (71%) | 63 (10%) | 43 of 46 pages |
| faymas.net | 954 | 0 | 70 | 884 (7 words) | 732 (77%) | 129 (14%) | 56 of 56 pages |
| faymas-in.com | 32 | 0 | 29 | 3 (3 words) | 13 (41%) | 32 (100%) | 3 of 4 pages |
| faymas.com.in | 10 | 0 | 1 | 9 (1 word) | 0 (0%) | 10 (100%) | 1 of 4 pages |
Nobody ships a missing alt attribute — 0 of 1,613 tags across all four domains. That is better than most of the web. But empty alt is a different problem, and it concentrates: 29 of faymas-in.com's 32 tags carry alt="", including every one of its content photographs. On a site whose product is pictures, the pictures have no description attached.
Dimensions are the other gap. Only 63 of faymas.in's 617 tags (10%) and 129 of faymas.net's 954 (14%) declare both width and height. Both sites know the dimensions — we read them out of the files themselves — they just do not put them in the markup. The two WordPress domains set them on 100% of tags, because WordPress computes them when the file is uploaded.
The social-preview layer is where faymas.in quietly does the best work of the four. Its prompt pages point og:image at that page's own hero output — 32 distinct preview images across 46 pages. faymas.net declares og:image on all 56 pages, but 41 of them point at the same /opengraph-image route, so 41 different pages present one picture when shared. faymas-in.com's homepage declares no og:image at all, and faymas-in.com is also the only one of the four that never declares a favicon — 0 of its 4 pages, against 46/46, 56/56 and 4/4 on the others.
So what is actually on these pages
Put the four measurements side by side and the image layer sorts the domains better than any other layer we have measured so far. faymas.in has 20,323 URLs and gives each prompt page its own real, distinct, immutable-cached photograph with a UUID for a name and an eleven-word alt text. faymas.net has 41 declared URLs, hides more behind them, serves its pictures from two development-grade object-storage buckets, and spends 76 KB twice per page re-fetching a logo it forbids anyone from caching. faymas-in.com has three posts and 6.27 MB of unoptimised PNGs behind 66 KB of HTML, with filenames that still say ChatGPT-Image. faymas.com.in has three files.
None of that is visible from the words on the pages. The text on these four sites is generated in much the same way by much the same templates — we measured that separately — but the files are not. Files have to exist. Somebody had to produce them, name them, upload them, and decide whether to cache them. On faymas.in that happened 20,000 times. On faymas.com.in it happened three times.
So if you want to know which of these four domains is a catalogue and which is a signboard, do not read the copy. Count the files.
Limits of this measurement
Server HTML only. We did not execute JavaScript, so any image injected after hydration is not counted; we did resolve data-src and the first srcset entry to cover the common lazy-loading pattern, but we did not simulate a browser. Page weight comes from one page per domain, chosen as a typical example, not from an average. The faymas.in sample is 46 pages out of 20,323 URLs, and the two WordPress domains are measured in full because four pages and three posts are all they have — that is a finding, not a sampling choice. Pixel dimensions were parsed from file headers; four sampled files — three SVG icons and one AVIF our parser does not read — have none and were excluded from the aspect-ratio figures. We counted url() references in inline stylesheets (570 on faymas.in, 0 on the other three) but did not fetch those assets. We did not measure Largest Contentful Paint, layout shift, or decode cost in a real browser, and we did not test what any search engine renders.
FAQ
How much of a faymas page is images?
On three of the four domains, more than the HTML: 1.68 MB of images behind 526 KB of HTML on a faymas.in prompt page, 1.88 MB behind 173 KB on a faymas.net gallery page, and 3.13 MB behind 66 KB on the faymas-in.com homepage. faymas.com.in is the exception at 0.18 MB behind 214 KB.
Are the images on faymas prompt pages real?
Yes on the three domains that have them. All 84 image requests we made returned HTTP 200, and every sampled file hashed differently: 15 of 15 on faymas.in, 13 of 13 on faymas.net, 13 of 13 on faymas-in.com. The duplication is in the tags, not the files — one logo fetched twice per page, one homepage fetching 6.27 MB across 12 tags.
How many images does faymas.com.in have?
Three distinct files across its four pages — Faymas-in.jpg at 2,094 bytes, plus two WebP files of 86,050 and 98,786 bytes. All ten of its image tags carry a base64 placeholder as their src; the real URL only appears in data-src.
Do these sites write alt text on their images?
None of the 1,613 image tags across the four domains is missing an alt attribute, but 29 of faymas-in.com's 32 tags have an empty one, including all of its content photographs. faymas.in writes real alt text on 609 of 617 tags, median 11 words.
Which faymas domain caches its images properly?
faymas.in and faymas.net both serve output images with cache-control: public, max-age=31536000, immutable. The exception on faymas.net is its own logo.png, served with max-age=0, must-revalidate and fetched twice on every page.
What is the largest image file we found?
A 2,475,704-byte PNG at 1672×941 on faymas-in.com, used as a featured image on its homepage. Its filename is two names glued together: ChatGPT-Image-Sep-23-2026-03_14_39-PM-1.webp followed by the post title.