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

Premium Carbon Black Floor Mat

90884

$249.95

Find the part that fits

  1. Make E-Z-GO
  2. Model TXT
Year
2006 2020

Start again

Order

Answer the questions above and we will show the one part that fits — out of 1.

Details

Madjax exclusive Carbon Premium Floormat delivers stunning aesthetics and textures without compromising durability, comfort or convenience 

Features: 

  • Pre-cut for OEM Pedal Groups and replaces factory rubber mat for a premium look and feel 
  • All Black Textured Custom Carbon Fiber Woven PVC upper layer with ¼” marine grade PVC foam backing 
  • Cooler to the touch with exceptional slip resistance in both wet and dry applications 
  • Tough on mold, mildew, tearing, and abrasion and easy to clean 
  • Made in the USA!

Product information

Applications

  • 2020 E-Z-GO TXT 2-Passenger
  • 2006 E-Z-GO TXT 2-Passenger
API reads behind this page 2 over the wire, 7 from cache · 28 ms total · template: product type
Method Path Source Status Time
GET /slugs('90884') cache 1h — —
GET /products/1012?$expand=items,media,attributes,related,applications,fitment,tabs,documents,modifiers cache 1m — —
GET /v2/products/1012?$expand=pricing network 200 16 ms
GET /slugs('90884') asked twice — —
GET /me cache 30m — —
GET /items(…)/attributes ×1 cache 30m — —
POST /v2/configurator network 200 12 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.