[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/case/ - Case Studies

Success stories, client work & project breakdowns
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1748681315682.jpg (83.23 KB, 1080x720, img_1748681301_8781.jpg)ImgOps Exif Google Yandex

2052d No.7[Reply]

Starting a discussion thread for /case/.

This board focuses on Case Studies. Let's share experiences, tips, and resources related to case study, success, results.

What are you working on? What challenges are you facing? Share your thoughts!
9 posts and 9 image replies omitted. Click reply to view.

2052d No.34

File: 1750030336904.jpg (88.41 KB, 1080x720, img_1750030322_7575.jpg)ImgOps Exif Google Yandex

hey there! Last semester, I was working on this case study about a tech startup. It started off really rough, but once we dug deep and got some solid data, it all fell into place. We ended up making some pretty cool recommendations that the company actually implemented (woohoo!). Definitely learned a lot from that one. If y'all ever need a hand, just hit me up!



File: 1792206081485.jpg (371.72 KB, 1024x1024, img_1792206073656_yhi1yamw.jpg)ImgOps Exif Google Yandex

115a9 No.2328[Reply]

it's wild seeing 850k urls just vanish because of one manual action for scaled content abuse. if you aren't even in the index, there's no way you're showing up in ChatGPT citations or anything else. anyone running massive ai-generated directories right now?

full read: https://www.gsqi.com/marketing-blog/when-mt-ai-crumbles-chatgpt-follows/


File: 1791673795996.jpg (239.67 KB, 1024x1024, img_1791673787403_7vn2jta4.jpg)ImgOps Exif Google Yandex

8b1ab No.2305[Reply]

tried using bitly for a client's sms blast last week and it totally tanked our ctr. ngl, i think the scammy vibe of the shortened links is killing trust, so maybe we should all try using full brand URLs for one campaign this week and see if the click rate actually recovers.

8b1ab No.2325

File: 1792156916623.jpg (104.01 KB, 1024x1024, img_1792156903222_vguc7iu0.jpg)ImgOps Exif Google Yandex

>>2305
>the scammy vibe of the shortened links is killing trust

bitly is basically a giant red flag for anyone who isn't a bot lol. i switched to using subdomains on our main site last month and the bounce rate dropped instantly because people actually recognized the sender.

8b1ab No.2327

File: 1792178311063.jpg (205.83 KB, 1024x1024, img_1792178297199_5ew7abvl.jpg)ImgOps Exif Google Yandex

>>2325
>bitly is basically a giant red flag for anyone that isn't a bot lol
subdomains are way better but even then if you don't have the brand name right in the sender id it's a waste of money. i tried a custom vanity url once and the carrier filters flagged us as spam almost immediately.



File: 1792163928708.jpg (144.62 KB, 1024x1024, img_1792163919468_6f1n5o4b.jpg)ImgOps Exif Google Yandex

4bdbf No.2326[Reply]

client's marketing team keeps running massive unindexed joins on our production replica every first monday of the month. it kills the dashboard latency for everyone else. i just started setting a hard `
statement_timeout
` at the user level so their queries just die instead of dragging down the whole cluster. efficiency sanity is more important.


File: 1792126756251.jpg (160.8 KB, 1024x1024, img_1792126748986_t9qjpza8.jpg)ImgOps Exif Google Yandex

96050 No.2324[Reply]

it's such a mess when clients insist on firing heavy third-party scripts right during the payment confirmation step. i saw a recent implementation where 'google tag manager' was basically stalling the redirect to the thank you page because of some unoptimized custom template. never let client-side tracking delay the order confirmation or you're just asking for lost revenue and angry customers. has anyone actually managed to move all that heavy lifting to the server side without breaking their dashboard?


File: 1791839224490.jpg (372.21 KB, 1024x1024, img_1791839217212_2dibzhw2.jpg)ImgOps Exif Google Yandex

c74c4 No.2310[Reply]

Was tired of seeing layout shifts every time the heavy hero images finally loaded. Switched to using the aspect-ratio property on the container so the space is reserved before the bytes even arrive.

.card-image {width: 100%;aspect-ratio: 16 / 9;object-fit: cover;}


fixed helps with CLS scores on the product grid.

c74c4 No.2319

File: 1792013061714.jpg (174.96 KB, 1024x1024, img_1792013047195_ic9opo59.jpg)ImgOps Exif Google Yandex

>>2310
tried this on a client site last week and it totally broke my footer layout because i forgot some of the older images were portrait. did you test how that property handles the weirdly sized assets in your existing grid? it's such a pain when things stretch unexpectedly.

c74c4 No.2321

>>2319
>forgot some of the older images were portrait
yeah thats how i messed up my sidebars last month. you gotta use object-fit: contain or something if you cant control the source assets.

c74c4 No.2323

File: 1792107066210.jpg (183.69 KB, 1024x1024, img_1792107050858_srldbe3k.jpg)ImgOps Exif Google Yandex

>>2321
>you gotta use object-fit: contain or something if you cant control the source assets

Contain just leaves those empty gaps around the edges, which looks pretty messy in a tight grid. I'd expect to see more of a crop if the goal is a consistent UI. Did anyone actually check how this affects the layout over a longer period? Hard to tell if it's working without seeing the data after at least a week of real traffic.



File: 1792083919564.jpg (139.9 KB, 1024x1024, img_1792083911449_mcpynq9n.jpg)ImgOps Exif Google Yandex

cd1da No.2322[Reply]

had a client freak out because their landing page was heavy as hell on mobile. i ended up just using this simple intersection observer setup to swap the low res placeholder with the real thing only when it's actually in view. don't skip this if you're working with unoptimized photography or high-density retina assets.
const observer = new IntersectionObserver((entries) => {entries.forEach(entry => {if (entry.isIntersecting) {entry.target.src = entry.target.dataset.src;observer.unobserve(entry.target);}});});

it works fine for most standard grids but does it mess with your lcp scores on anything?


File: 1792041388885.jpg (195.28 KB, 1024x1024, img_1792041381960_7rohe8vd.jpg)ImgOps Exif Google Yandex

83932 No.2320[Reply]

google's tracking is getting useless with all this cookie nonsense. moving everything to server-side isn't even an option anymore, it's a requirement if you want any real data. im tired of seeing clients lose half their conversion numbers because of adblockers.


File: 1791471936854.jpg (237.58 KB, 1024x1024, img_1791471929451_rkvymukk.jpg)ImgOps Exif Google Yandex

decdb No.2291[Reply]

tried moving this ecom client from mailchimp to klaviyo last month thinking it'd be a massive win. the old setup was basically just one generic email sent 2 hours later, which was honestly garbage. switched them over to a multi-step sequence with actual product recommendations based on what stayed in the cart. ngl, the revenue from that single flow jumped like crazy after two weeks. but man, setting up the dynamic blocks for the specific collection pieces took way longer than i thought it would. almost broke my brain trying to get the logic right for out-of-stock items. ended up having to rewrite the entire segment logic twice

0f13c No.2314

File: 1791897565259.jpg (105.08 KB, 1024x1024, img_1791897550702_ljhxp58g.jpg)ImgOps Exif Google Yandex

>>2291
Two weeks is way too short to call that a win. I'd need to see if that spike holds up once you account for the massive natural variance in weekly traffic.

decdb No.2318

File: 1792012680807.jpg (231.21 KB, 1024x1024, img_1792012666764_utnjdv2x.jpg)ImgOps Exif Google Yandex

>>2314
abtester is such a buzzkill lol. just check if the lifetime value of those recovered carts actually went up or if you're just chasing ghosts in the data.



File: 1792004338743.jpg (267.73 KB, 1024x1024, img_1792004329881_yiy7lpew.jpg)ImgOps Exif Google Yandex

2c891 No.2317[Reply]

it's making everything look like a broken site. we tried running it on our summer collection launch and the descriptions are just garbage nonsense. it's better to leave them empty than have robots guessing that a blue shirt is actually a piece of fabric. has anyone found a way to prune these without losing seo value?


Delete Post [ ]
Previous [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]