[ 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: 1792407955448.jpg (158.46 KB, 1024x1024, img_1792407947382_yiwzycef.jpg)ImgOps Exif Google Yandex

3e2b8 No.2336[Reply]

finally found something that might save me some headache. i was literally just staring at a blank repo yesterday trying to figure out if i could use a specific name for this new client project without realizing the npm package was already taken. this caniname tool lets you run an npx command to check both netlify subdomains and npm availability in one go. it even shows you the links to the existing sites if they are occupied. the dev actually had to rename his own tool from namecheck because it was already snagged. ngl i wonder if adding more services is as easy as he says or if it gets messy once you add things like vercel or something. might be worth a try next time i am stuck in that manual checking loop.

found this here: https://www.bram.us/2026/10/08/caniname-cli-tool-to-check-project-name-availability/


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?

2c891 No.2333

>>2317
>it's better to leave them empty than have robots guessing

did this exact thing for a fashion client last year and the 'fabric' descriptions actually tanked our conversion because people thought the site was a scam lol. just use google vision api to at least pull the color and category so it's not totally random nonsense.

2c891 No.2335

File: 1792387473439.jpg (219.47 KB, 1024x1024, img_1792387431003_tvmkayr3.jpg)ImgOps Exif Google Yandex

>>2333
Google Vision is better than nothing, but it still misses the nuance of things like texture or fit. I'm curious which specific AI model you guys are using for the summer launch right now? My last attempt at automation produced descriptions that were way too long and looked super suspicious to our users.



File: 1792285697275.jpg (137.37 KB, 1024x1024, img_1792285686819_f2pc26d0.jpg)ImgOps Exif Google Yandex

38286 No.2330[Reply]

The ROAS looks way too high on our internal dashboard compared to what the client is seeing in GA4. I've already checked the session vs user settings, but I'm still not convinced this isn't just a lucky seasonal spike hitting during a period of low organic traffic.


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: 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: 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: 1791961502524.jpg (199.61 KB, 1024x1024, img_1791961494802_wnvpthq3.jpg)ImgOps Exif Google Yandex

ebcb5 No.2316[Reply]

switched our cluster to that new version of redis last night thinking it would be a quick win. everything crashed because i messed up the eviction policy settings.
>everything crashed
lmao my bad, but hey at least we learned something about testing properly next time definitely next time.


File: 1791918731212.jpg (177.66 KB, 1024x1024, img_1791918720949_2v023xva.jpg)ImgOps Exif Google Yandex

b507a No.2315[Reply]

saw this case study for Farm Minerals and it's wild that up to 70% of nitrogen just evaporates or washes away. adelt is trying to frame the whole thing around efficiency rather than just some vague sustainability pitch, which makes sense if you want farmers to actually buy in. still not sure how they're going to track the actual field performance data without it getting lost in a mess of unverified user reports.

more here: https://www.awwwards.com/farm-minerals-case-study.html


File: 1791881991762.jpg (267.98 KB, 1024x1024, img_1791881983445_wnzfzm4b.jpg)ImgOps Exif Google Yandex

d5ce5 No.2313[Reply]

was looking at some recent logs and noticed we're letting way too many flagged transactions through because the threshold is set way too high for the current volume.
>the risk level looks low enough to pass
it's clearly not working since our chargeback rate is spiking. what's everyone using for their manual review queue?


Delete Post [ ]
[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 ]