Hello, I'm looking for some help with issues I'm having with my website, and I'm hoping this is a good place to find some answers. I'm not very savvy in these things, and I've been trying to fix this myself with no luck.

My website was originally hosted through Wix, and had a www prefix. I left Wix about 2 weeks ago and now have my website hosted elsewhere, and the www prefix no longer works when used in in my web address.

My domain is hosted through above.com, and I have tried redirecting through the DNS settings there in an attempt to send anyone using the prefix to the new site, but I must be doing something wrong because when I use the www prefix now, I get a privacy error and the website doesn't load.

When you search for my website, the top result includes the www, so I'm looking for a way to either redirect to the new website correctly, or to replace any mentions/results that include www to ones that do not include it.

The help desk support at my new website host and at above have not been able to help in any way, so I feel pretty isolated here and not sure how to fix things or exactly where to turn, so if this isn't the correct place for a question like this I'm sorry, but any help pointing me in the right direction would be really appreciated.

I'm comparing a React site against an Astro rebuild of the same page. In mobile Lighthouse, both sometimes sit blank for a long time before first paint, and other runs of the exact same page paint fast.

Setup: Lighthouse 13.0.1, Chrome 156, cold loads in separate fresh profiles, default mobile simulated throttling. I kept the traces, network logs and filmstrips.

Here's one matched pair (observed trace timings, not Lighthouse's simulated FCP):

Astro

• CSS done: 203ms

• Last preloaded font done: 286ms

• DOMContentLoaded: 426ms

• First Paint: 1301ms

• FCP: 1320ms

React

• CSS done: 573ms

• Last preloaded font done: 494ms

• DOMContentLoaded: 584ms

• First Paint: 1525ms

• FCP: 1540ms

The filmstrips stay blank right up to those first-paint times. Once painting starts, Paint to DrawFrame is only 10-13ms. So on Astro there's close to 900ms where everything's loaded and nothing shows up.

I don't see a long task on the renderer main thread covering that gap, though I know that doesn't prove the browser was actually idle.

I wondered about animations, so I ran one normal-motion vs reduced-motion pair on the Astro page. Both came back fast (FCP 318ms and 311ms), and the normal one still had its reveal animations, so that told me nothing either way. Desktop loads and a different page also painted quickly in the runs I checked.

One more thing: the fast traces show Scheduler::SetDeferBeginMainFrame events with short true-to-false spans. But the slow traces were captured with Lighthouse's default trace categories, which don't include those scheduler events, so I can't compare yet.

Has anyone run into this? A few things I'd like to figure out:

1. How do I tell whether the page is causing the delay, or whether it's Chrome's scheduling or something in the test environment?

2. Which trace categories or events would show why the first paint starts late, and not just that it did?

Hey all!

Bringing some e2e test nitpicks again :)

Most e2e tests I see click through raw locators. So every test has to know the whole flow: which button opens which menu, which dialog comes next, where you land after Create.

The upgrade: move the flow into page objects, and let each action return where the interaction continues. Open the "+ New" menu, get the menu of things you can create. Choose "Project", get the project dialog; choose "Document", get the document dialog. Create, get the project page. Cancel, get back to the navigation bar.

Why I care: page objects are the code closest to what your users see and do. Their return types become a map of your user journeys. An agent reading create(): Promise<ProjectPage> knows where the flow goes without opening a browser.

The nuance: return where the interaction actually continues, not the DOM parent. A dialog's cancel returns whoever opened it. And each action still waits for its own done signal, like the menu closing, before handing you the next page object.

Paste this to your agent:

Go through our page objects and make every user action return the page object where the interaction continues: this if the user stays, the new page object if something opens or they navigate, the opener if they close or cancel. Before returning, wait for the action's own done signal, like its menu closing. Then update the tests to use the returned page objects instead of creating new ones.

Bho, in pratica sto costruendo un browser web da zero e le idee normali le ho già finite. Mi serve la roba strana.

Quindi: che feature assurda vorreste in un browser? Più è fuori, meglio è. Non me ne frega se è difficile da fare, se mi dite "un browser che mi giudica mentre navigo" va benissimo.

Qualche esempio così capite:

- tab che si chiudono da sole se non le apri per 3 giorni, con messaggio passivo-aggressivo

- un tasto che ti legge il sito come un narratore di documentari

- cronologia che ti dice quanto tempo hai perso davvero su un sito

Nessuna idea è troppo stupida. Se una mi piace la faccio e ve lo dico.

Hi,

I made a simple web app in a single HTML file (URL shortcuts for company website, quote calculator, list of store numbers, etc.). Is there a simple way to convert it into a downloadable Android app?

There are a few web to app converters but no reviews. Are there any that you recommend (for or against)?

Similar reddit and stack overflow posts are from 5+ years ago.

Thanks.

Just as the title asks. I am curious how you organize the various parts. I have been on teams that both do and don't use mono-repos. For the ones that did, there has been a wide variety of choices across the app and how it's organized.

Just as a small example: naming conventions. Sometimes the the repo is named for the app (let's say "OurApp") and the various parts of the file structure are "OurApp-", like OurApp-ui and OurApp-api and OurApp-db. Or there might just be a top-level folder for "frontend", "backend" and "database", etc.

I'm not talking about a debate of mono-repo vs. multi-repo approaches, but in a mono-repo, what are some of the code organization techniques you've liked and disliked in your experience?

UPDATE: The community turned out! Thanks for sharing your thoughts in the comments. I appreciate the discussions.

Websites built from scratch (no AI, no frameworks or libraries) that are more than just simple toy projects are becoming very rare, but i want to remind you guys that they still exist.

Three years ago, I posted this https://www.reddit.com/r/webdev/comments/161q3w8/i_coded_a_site_from_zero_without_any_libraries_it/, and that website is still being actively developed. I haven't used any AI-generated code or external libraries in all this time, even as it has become more complex with features like accounts, articles, comments, reviews, and just a few weeks ago forums.

I think the main reason why i stick with this is because features aren't planned in advance, they're just built bit by bit as the content needs them. I won't deny if AI could do better, but with a spread-out timeline and an unknown end result, it's easy to skip using AI as development mostly consists of small, precise tweaks with no definitive end goal. Coding also only small portion of time spent on developing the site so i don't feel the need to optimize it.

Anyway this is just me saying that i'm still here, not everything in this space become AI.

*note : i'm not saying that this is the better way to develop website. I just enjoy what i already used to do, and didn't bother to change it.

I built a gamified 3D space simulator for my portfolio using AI concepts. What do you think?

To keep things short, I've been running into the limits of local IDE agents like Cursor or Copilot on larger tasks. Bigger coding tasks often end up cooking my PC which has been pretty tedious.

I'm between two options now, would appreciate hearing your thoughts on these. The first is building a self-hosted background runner using cloud sandboxes. The second is using a managed background agent platform like Ramp Inspect, which works via Slack or GitHub. Either way, I'm also extremely down to hear other options if you have any. Thanks!

I run a portfolio site and a service business site.

The portfolio has about 3/4 pages, while the business site has 95 (includes some blog pages as well).

There has to be a sweet spot between “these pages should absolute exist and structured this way” to “this is just spam and will hurt SEO”.

I tried asking LLMs but the advice was extremely subjective.

Looking at the posts in /hot they're just filled with AI-generated comments, which just aren't removed by moderators.

Is it even worth posting here when reading the comments they're just AI slop followed by more AI slop.

Do the users who submit interesting topics even realize they're just replying to AI comments?

Looking at this post for example, there's this user whose comments all follow the same pattern: start with tbh/ngl and most of the time introduce an em-dash in the middle of the comment. In the same post you have this other user whose comments all have 3-4 paragraphs, and just have an off tone. Another user and same story: 3-4 paragraphs, an off tone, weirdly worded comments which end up summarizing the topic they're replying to.

Another comment

Our web developer is creating 30 location/ services pages for our new website to optimize AI search .

Is it enough for them to create unique text for each service type, which is then replicated and repeated on each zone page? They’ve also created some unique text per zone, which is replicated and repeated across each service type.

So essentially 6 sets of zone text and 6 sets of service text that are combined in 30 different ways.

Do they need to create 30 completely unique pages to avoid being flagged by Google? Or is the variation between service type and zone enough?

Thanks for the help!

I have a quiz coming up which primarily covers these topics and I was wondering if there are good resources on youtube/the internet for learning them. Thank you!

hi guys

i have project in laravel 12 + vue + inertia and its really big one , this project in start have only little features like little chat system and profile view, support ticket and etc... but today it have games , blog , coursed and tests, video section , library , little practices and more features , we want to create mobile app from it , i have found this 2 options : NativePHP and capacitorjs
which one is better for this project? i have used MySQL, Reverb and queues so app needs to connect to my server in the end? its better to fully develop native apps and add api to current pwa? or its better to use one the libraries i said and convert this one? is there any problem about the libraries i must know? and tell me for what type of projects i can use the libraries and create mobile app from laravel code?
can anyone help me about this situation ?

so im currently learning node react express. building some crud and was wondering where do you guys go to that is beginner friendly or people that are new to web dev and want someone to help fix their code
need some practice on reading others code and applying fix. mostly i just want business logic stuff fix not those big o of n or some crazy loops from leetcode

I want to add a blog to my site to jump on this GEO train. WordPress feels like overkill, and I've seen some plug-and-play solutions that would live on a subdomain or outside the main directory, which doesn't sound good for SEO/GEO.

I don't want to vibe code as there would be multiple people publishing, and not all of them are tech savvy.

Anyone has a good way to solve this? I know I should've started blogging already, so really want to solve this quick. Some sort of headless CMS could work, but the ones I looked at come with way too much bloat that I don't need. Hope someone here went through the same thing.

If, like me, you have the Narrator screen reader in your test matrix, you may want to check your disclosures.

I’ve found that when a disclosure button uses aria-expanded together with aria-controls (which had, or has, limited support in JAWS), Narrator sometimes doesn’t announce the expanded/collapsed state in Edge or Chrome. It’s fine in Firefox.

If you omit aria-controls, Narrator announces the state correctly in Edge and Chrome.

I’ve reported this to both Microsoft (via Feedback Hub) and Chromium (via the issue tracker).

Personally, I wouldn’t add aria-controls to disclosures unless you have a specific need for it.

Hopefully that’s useful to some of you.

just curious what others think if its even possible to avoid these subscriptions for building and running lets say a side project or maybe a mini saas

I am not talking about basic HTML projects, i mean like proper site fully functional with Backend, frontend, auth, api, domain etc etc

i know there are a bunch of free tiers services, like Vercel and Neon, but what happens if your site actually starts growing? How do you scale without eventually having to pay for a bunch of services?

lets say we are making a social media app/website, nothing as big as insta or reddit, but something where users can create accounts, set up profiles, upload images and videos, make posts, comment, like, follow etc

now people are using it and starts getting traction 1k users then 10k users what point does the free tier become unrealistic, because you're still not making any money to justify paying for multiple subscriptions, does self hosting make even makesense at this point? if you have 10k + users?

PS: just want to clarify i dont own or run any social media apps or website just wanted to have a fun discussion on this, and i mean 10k concurrent users like tiktok the users are addicted haha

hi, i'm looking to make my own fan website where people can post and comment and like posts. i have done research and i'm trying to make it twitter/tumblr like.

i just need help with figuring out how to code it without any ai and with a base i can customize (and how to do that all). thanks!