More tables or More records performance wise
Both of these schema anti-patterns have been repeatedly refuted:

Do not have multiple 'identical' tables.

Do not spread an array across columns.


So have one table with lots of rows:
    sites
       id
       url
       region
       value
       date_created
       tech_category

Use suitable composite indexes for efficiency.  (We need to see your SELECTs to advise further.)
Use &quot;pivoting&quot; to make the 4 region columns.  (Or &gt;4 when you increase the number of regions.)
As for &quot;performance&quot;...  If you don't have a billion rows, performance is probably not a problem.  When the table gets that big, we can discuss &quot;summary tables&quot;.