Distributor demo storefront, built on the PIMento API Sign in
Product image

Golf Cart Windshield

Windshield

$120.99 and up

Find the part that fits

  1. Year 2020
  2. Make E-Z-GO
  3. Model Express L6

That is the one. The part below fits your configuration.

Start again

Order

WINDSHIELD, EZ TXT BOLT, FD, CLEAR, IMP MOD
35333 · Out of stock
$160.95

Specifications

Condition New
Unit Each

Product information

  • 2020 Club Car Onward 2 Passenger 2-Passenger
  • 2020 Club Car Onward 4 Passenger Mutli-Passenger
  • 2020 Club Car Onward 6 Passenger Mutli-Passenger
  • 2020 Club Car Onward HP Mutli-Passenger
  • 2020 Club Car Onward HP Li-Ion Mutli-Passenger
  • 2020 Club Car Onward Lifted 4 Passenger Mutli-Passenger
  • 2020 E-Z-GO 2Five 2-Passenger
  • 2020 E-Z-GO Express 4x4 2-Passenger
  • 2020 E-Z-GO Express L6 Mutli-Passenger
  • 2020 E-Z-GO RXV 2-Passenger
  • 2020 Yamaha The Drive2 - Fleet 2-Passenger
  • 2020 Yamaha The Drive2 - PTV 2-Passenger
  • 2019 E-Z-GO RXV 2-Passenger
API reads behind this page 2 over the wire, 6 from cache · 50 ms total · template: Default Configurator
Method Path Source Status Time
GET /products/1013?$expand=items,media,attributes,related,applications,fitment,tabs,documents,modifiers cache 1m — —
GET /v2/products/1013?$expand=pricing network 200 25 ms
GET /slugs('Windshield') cache 1h — —
GET /me cache 30m — —
GET /items(…)/attributes ×4 cache 30m — —
POST /v2/configurator network 200 25 ms
GET /categories cache 15m — —

204 and 404 both mean “no rows” on this API — which of the two an endpoint uses is per-endpoint, and the client maps both to an empty result rather than an error. Collections come wrapped in an OData envelope and are capped at 100 rows per page.

Rows marked cache were answered from memory, and the time beside each is how long that kind of read is held; one marked asked twice is something this page had already read while rendering, so it cost nothing either way. Catalog reads are cached by rate of change rather than on one site-wide timer:

Pricing and stock are read live on every view — there is no setting that caches them. That is why a warm product page still makes exactly one request: everything else on it came from memory.

The catalog can also drop all of it at once rather than waiting for a tier to lapse, by calling POST /hooks/cache when it publishes.