WP Go Maps Block
The easiest to use Google Maps and Open Layers Map Plugin is now available as a standalone map block! Create a custom map block with high-quality markers and add them to your WordPress posts and pages effortlessly. Perfect for contact pages, business locations, event venues, and more! Map blocks are lightweight and deliver optimal performance, ensuring a seamless experience for your WordPress site. They’re easy to customize, allowing you to quickly add and configure maps to suit your needs without compromising site speed or performance. If you need more features like multiple markers, shapes, and a store locator, our full (free) WP Go Maps plugin might be perfect for you. Block Features Add unlimited map blocks to your posts/pages Choose between Google Maps or OpenLayers for each block Edit your marker directly from the block editor Set marker location by free location search, or by right-clicking on the map preview Preview your map in real time, within the block editor Easy to use and customize without any coding experience Control width, height and alignment of your maps From the team that brought you the most popular Google Maps plugin on WordPress Lightweight for optimal performance No database queries or tables Basic info-window for your marker Control zoom level of your map Support for localization Latest Google Maps API Latest OpenLayers API Already using WP Go Maps? You can still use this block for single locations, as it is fully integrated with both our basic and Pro versions! References We make use of a various libraries and 3rd party service providers in order to render maps in your preferred mapping engine. This section will describe each of these in more detail and when they are used. OpenLayers: Served from a local library file (lib/ol.js & lib/ol.css), provided by OpenLayers. We use this library when you set your block to use OpenLayers (default). You can find the source files on the OpenLayers GitHub. OpenStreetMap: When you select the OpenLayers engine, a default map tile server is used, which is provided by OpenStreetMap. This is a 3rd party service provider that we rely on to render your map. They may also make use of MapBox for some of their assets. Google Maps API: If you decide to use Google Maps as your map engine, we will include the Google Maps API as a 3rd party service provider that we rely on to render your maps. In this case, admin map previews are still rendered by OpenLayers and OpenStreetMap. Nominatim (OpenStreetMap): If you perform an address search within the admin area, we will make use of the OpenStreetMap Nominatim to lookup locations and suggest addresses to you. This is a 3rd party service provider that we rely on for address searches.
Top keywords
- maps13×2.81%
- map12×2.60%
- block8×1.73%
- openlayers8×1.73%
- google7×1.52%
- google maps7×1.52%
- openstreetmap5×1.08%
- 3rd4×0.87%
- 3rd party4×0.87%
- 3rd party service4×0.87%
- api4×0.87%
- party4×0.87%
Static Posts for Twitter – Embed x.com Tweets without an iframe
The standard Tweet, or Post (or Xeet?), loads in 500kb of front end JavaScript, tracking cookies, and lots of noise. This plugin avoids all of that by pre-rendering the entire Tweet statically. Say goodbye to bulky Tweets! https://github.com/KevinBatdorf/wp-xeet Features Embed a Tweet/Post/Xeet without an iframe Save 500kb of page load No Twitter/X cookies, tracking, JavaScript, etc Static – Twitter/X changes won’t affect your site Dark/light auto mode Vercel The Tweets are parsed on a server hosted on Vercel. Using this service, and thus connecting to their servers, you agree to their privacy policy and terms. NOTE: Your frontend does not rely on any api calls, and if the Vercel api shuts down tomorrow, your site will not be affected in any way.
Top keywords
- tweet3×2.29%
- vercel3×2.29%
- 500kb2×1.53%
- api2×1.53%
- cookies2×1.53%
- javascript2×1.53%
- post2×1.53%
- site2×1.53%
- tracking2×1.53%
- tweets2×1.53%
