{"id":859,"date":"2025-03-24T14:27:52","date_gmt":"2025-03-24T14:27:52","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/server-side-vs-client-side-marker-clustering\/"},"modified":"2025-04-03T15:24:12","modified_gmt":"2025-04-03T14:24:12","slug":"server-side-vs-client-side-marker-clustering","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/marker-cluster\/server-side-vs-client-side-marker-clustering\/","title":{"rendered":"Server Side vs Client Side Marker Clustering"},"content":{"rendered":"<p>\n\tMarker Cluster extension for GeoDirectory lets you choose between <strong>Server Side <\/strong>and <strong>Client Side <\/strong>marker clustering. Each has its own distinct advantages.&nbsp;<\/p>\n<h2>\nServer Side Marker Clustering<\/h2>\n<p>\n\tIn simple words, <strong>Server Side Marker Clustering<\/strong> loads just the basic cluster info. All map-related calls are made via API requests instead of AJAX.&nbsp;<\/p>\n<section class=\"alert alert-info\">\n\tServer Side Marker Clustering causes lesser overload and is ideal for larger directories and sites with thousands of listings. Theoretically, it can handle infinite amount of listings, and has been tested with millions of listings.<\/section>\n<h2>\nClient Side Marker Clustering&nbsp;<\/h2>\n<p>\n\tIn <strong>Client Side Marker Clustering, <\/strong>the clustering itself as well as all the markers are loaded in the memory of the browser for faster page load times. While this provides a significant page speed boost, it can also slow down the website or even worse, make the page unresponsive if there are too many listings.&nbsp;<\/p>\n<section class=\"alert alert-info\">\n\tSince Client Side Marker Clustering relies on browser memory, it can load pages much faster.&nbsp;<\/section>\n<h2>\nWhich One to Use and How to Change?<\/h2>\n<section class=\"alert alert-warning dashed\">\n\tAs a rule of thumb, it is a good idea to use Client Side Marker Clustering for smaller directories of up to, say, 500 listings. For larger directories, you should opt for Server Side Marker Clustering.&nbsp;<\/section>\n<p>\n\t<img width=\"920\" height=\"468\" src=\"https:\/\/wpgeodirectory.com\/documentation\/wp-content\/uploads\/2025\/03\/file-kTPtSztoEo-1.png\" class=\"attachment-large size-large\" alt=\"\" decoding=\"async\" loading=\"lazy\" srcset=\"https:\/\/wpgeodirectory.com\/documentation\/wp-content\/uploads\/2025\/03\/file-kTPtSztoEo-1.png 1007w, https:\/\/wpgeodirectory.com\/documentation\/wp-content\/uploads\/2025\/03\/file-kTPtSztoEo-1-300x153.png 300w, https:\/\/wpgeodirectory.com\/documentation\/wp-content\/uploads\/2025\/03\/file-kTPtSztoEo-1-768x390.png 768w\" sizes=\"auto, (max-width: 920px) 100vw, 920px\" \/><\/p>\n<dl>\n<dt>1<\/dt>\n<dd>\n\tTo change between Client Side and Server Side Marker Clustering, navigate to <strong>GD &gt; Settings &gt; Marker Cluster. <br \/>\n\t<\/strong> <\/dd>\n<dt>2<\/dt>\n<dd>Therein, choose the <strong>Cluster Type <\/strong>that suits you, and save your changes.\n\t<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"<p>Marker Cluster extension for GeoDirectory lets you choose between Server Side and Client Side marker clustering. Each has its own distinct advantages.&nbsp; Server Side Marker Clustering In simple words, Server Side Marker Clustering loads just the basic cluster info. All map-related calls are made via API requests instead of AJAX.&nbsp; Server Side Marker Clustering causes [&hellip;]<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[554,649],"article\/categories":[405,213],"class_list":["post-859","gd_place","type-gd_place","status-publish","hentry","gd_place_tags-geodirectory-extensions","gd_place_tags-marker-cluster","gd_placecategory-marker-cluster","gd_placecategory-extensions-features"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/859","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/types\/gd_place"}],"replies":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/comments?post=859"}],"version-history":[{"count":0,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/859\/revisions"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=859"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=859"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=859"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}