Hi everyone,
I’m currently working on a small project related to namaz vakitleri and I’ve run into a structure/performance issue. Maybe someone here has experience with large dynamic location-based websites.
My setup currently includes:
Multiple city pages
Daily prayer times (Imsak, Gunes, Ogle, Ikindi, Aksam, Yatsi)
Data updates every day automatically
Different URLs for each city
Example structure:
/turkiye/istanbul-namaz-vakitleri.html
/turkiye/ankara-namaz-vakitleri.html
/turkiye/izmir-namaz-vakitleri.html
Right now I’m fetching prayer times dynamically and caching some data locally.
The problem is:
As pages increase, performance starts slowing down
I’m not sure if I should:
store all prayer times in database
use static JSON files
or continue using external APIs
Another issue:
Google indexing behaves strangely for some dynamically updated pages. Some pages get crawled but stay in “Crawled – currently not indexed” for a while.
I checked a few similar projects like namaz vakitleri
and noticed many of them use lightweight structures with cached daily data.
Questions:
What’s the best structure for scalable city-based prayer time pages?
Better to use API or pre-generated static files?
Any SEO tips for frequently updated prayer-time content?
Best way to handle daily cache refresh without slowing the server?
Would love to hear real-world suggestions from developers who worked on location-based or time-based websites.
Top comments (2)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.