Website review, no card needed
88.pictures website review
Visit site (opens in a new tab)Reviewed 29 October 202640 issues · 82 checks
This review found 40 issues worth fixing on 88.pictures, 16 of them high impact, across 82 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 104 ms |
| May 16, 2026 | 100 ms |
| May 23, 2026 | 95 ms |
| May 30, 2026 | 90 ms |
| Jun 6, 2026 | 90 ms |
| Jun 13, 2026 | 93 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 98 ms |
| Jul 11, 2026 | 97 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 97 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 99 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 98 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 98 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 93 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Improve image delivery
2.5 s · 8.5 MB29 images could be 8.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Render-blocking requests
3.6 s41 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
2 third-party services on the page
2 third-party services load with your homepage (Vimeo and Google Fonts), adding 13.0 MB and 251 ms of main-thread time.
Vimeo adds 251 ms
251 msVimeo costs a phone 251 ms of main-thread work and 12.9 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.
Reduce unused JavaScript
581 KiBAbout 581 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
300 ms · 12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
1,517 HTML elements
The page has 1,517 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 165 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
104 KiB9 files are served with short cache lifetimes, so returning visitors download them again (104 KiB).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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: 350 ms
350 msYour server sent the HTML in 350 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user CLS: 0.63
0.63For real visitors the layout shifts by 0.63 (75th percentile). Good is under 0.1.
Speed Index: 18.6 s
18.6 sVisually, the page fills in at 18.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 30.0 s
30.0 sThe page becomes fully interactive after 30.0 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.639
0.639The layout shifts by 0.639 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 5.5 s
5.5 sYour largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “88 PICTURES”.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 104 ms to 93 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 115 ms
115 msReal visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 36% faster for real visitors
-36%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 121 ms
121 msScripts block the page for only 121 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 30.7 MB in 181 requests
30.7 MBYour homepage downloads 30.7 MB in 181 requests on a phone: images 17.6 MB (55), other files 11.8 MB (39) and scripts 1.1 MB (35). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 4.0 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
1.7 MB5 images are downloaded at several times the size a phone draws them, for example MV5BMDVlZTEwMTItNmE4Zi00ZGFhLWI4NjgtMDdiZTA5NDdmNWYyXkEyXkFq at 3,158 px wide, shown at 310 px. Resized copies would save about 1.7 MB.
30 images in older formats
30 images (9.3 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.
5 images below the first screen load straight away
5 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 8.7 g of CO₂ per visit
8.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.71 g of CO₂e: 1045.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
30 links without text
30 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “Home - 88pictures”. Between 30 and 65 characters leaves room to say what you do and for whom.
28 H1 headlines
There are 28 <h1> headlines (“Baahubali: The Eternal War”, “High In The Clouds” and “An Almost Christmas Story”). One clear main headline is easier for people and search engines.
92 internal links, 11 external
The homepage links to 92 pages on 88.pictures and 11 external pages.
6 checks passed
Meta description: 129 characters
Your meta description is 129 characters: “We envision stories and engineer imagery by creating experiences that resonates universally.We create stories that fasc…”.
Canonical URL set
The canonical URL is https://88.pictures/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://88.pictures/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://88.pictures/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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (265 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://88.pictures/animation, https://88.pictures/portfolio/baahubali-the-eternal-war, https://88.pictures/portfolio/high-in-the-cloud, https://88.pictures/portfolio/an-almost-christmas-story, https://88.pictures/portfolio/bandits-of-golak and https://88.pictures/portfolio/5-more-sleeps-till-christmas-2 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://88.pictures/animation has no <h1> headline, so visitors and search engines get no clear main topic.
14 pages with very little text
https://88.pictures/portfolio/baahubali-the-eternal-war, https://88.pictures/portfolio/high-in-the-cloud, https://88.pictures/portfolio/an-almost-christmas-story, https://88.pictures/portfolio/bandits-of-golak, https://88.pictures/portfolio/5-more-sleeps-till-christmas-2 and https://88.pictures/portfolio/fast-furious-spy-racers-2 and 8 others 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
8 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 181 words
The homepage has only about 181 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact Us”.
Direct contact links
Visitors can reach you directly: 0 phone links and 8 email links.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies, 2 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 88.pictures, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- Vue.js
- Hosting
- Hostinger
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 88.pictures, including 20 speed issues, 2 SEO issues and 4 conversion gaps. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.