<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Deez Smith</title>
    <description>The latest articles on DEV Community by Deez Smith (@info_deez90).</description>
    <link>https://dev.to/info_deez90</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3930125%2Ff784ff02-2091-41ac-b01c-3abbc7de7aac.png</url>
      <title>DEV Community: Deez Smith</title>
      <link>https://dev.to/info_deez90</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/info_deez90"/>
    <language>en</language>
    <item>
      <title>How to Build Dynamic Namaz Vakitleri Pages for Multiple Cities?</title>
      <dc:creator>Deez Smith</dc:creator>
      <pubDate>Wed, 13 May 2026 21:19:00 +0000</pubDate>
      <link>https://dev.to/info_deez90/how-to-build-dynamic-namaz-vakitleri-pages-for-multiple-cities-23id</link>
      <guid>https://dev.to/info_deez90/how-to-build-dynamic-namaz-vakitleri-pages-for-multiple-cities-23id</guid>
      <description>&lt;p&gt;Hi everyone,&lt;/p&gt;

&lt;p&gt;I’m currently working on a small project related to &lt;a href="https://vakitlerinamaz.com/" rel="noopener noreferrer"&gt;namaz vakitleri&lt;/a&gt; and I’ve run into a structure/performance issue. Maybe someone here has experience with large dynamic location-based websites.&lt;/p&gt;

&lt;p&gt;My setup currently includes:&lt;/p&gt;

&lt;p&gt;Multiple city pages&lt;br&gt;
Daily prayer times (Imsak, Gunes, Ogle, Ikindi, Aksam, Yatsi)&lt;br&gt;
Data updates every day automatically&lt;br&gt;
Different URLs for each city&lt;/p&gt;

&lt;p&gt;Example structure:&lt;/p&gt;

&lt;p&gt;/turkiye/istanbul-namaz-vakitleri.html&lt;br&gt;
/turkiye/ankara-namaz-vakitleri.html&lt;br&gt;
/turkiye/izmir-namaz-vakitleri.html&lt;/p&gt;

&lt;p&gt;Right now I’m fetching prayer times dynamically and caching some data locally.&lt;/p&gt;

&lt;p&gt;The problem is:&lt;/p&gt;

&lt;p&gt;As pages increase, performance starts slowing down&lt;br&gt;
I’m not sure if I should:&lt;br&gt;
store all prayer times in database&lt;br&gt;
use static JSON files&lt;br&gt;
or continue using external APIs&lt;/p&gt;

&lt;p&gt;Another issue:&lt;br&gt;
Google indexing behaves strangely for some dynamically updated pages. Some pages get crawled but stay in “Crawled – currently not indexed” for a while.&lt;/p&gt;

&lt;p&gt;I checked a few similar projects like namaz vakitleri&lt;br&gt;
 and noticed many of them use lightweight structures with cached daily data.&lt;/p&gt;

&lt;p&gt;Questions:&lt;/p&gt;

&lt;p&gt;What’s the best structure for scalable city-based prayer time pages?&lt;br&gt;
Better to use API or pre-generated static files?&lt;br&gt;
Any SEO tips for frequently updated prayer-time content?&lt;br&gt;
Best way to handle daily cache refresh without slowing the server?&lt;/p&gt;

&lt;p&gt;Would love to hear real-world suggestions from developers who worked on location-based or time-based websites.&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>discuss</category>
      <category>performance</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
