Tools
SERPerator
Live test to see Google mobile and desktop visibility - PPC, SEO & Other.
Page-oscope
Live test to see competitors landing pages in any country - Mobile & Desktop.
App Rankalyzer
See live Google App Pack Ranking results by country and keyword.
SERP Datalyzer
Track search result visibility over time. See visual search results images & parsing about rank, pixels from the top and more.
Page Datalyzer
Track landing pages and page code over time - for you or a competitor.
App Datalyzer
See how your apps and competitive apps rank for keywords in the Apple App Store and Google Play - track in any country and language.
API Integrations
Add Page-o-Scope or SERPerator utilities to your site!
Resources
Request Consulting
Request the consulting proposal from our team of ASO and SEO experts.
Request Training
Reach out to our team for bespoke training.
Request a Tool Demo
Request a guided walkthrough of our leading rank tracking and page testing tools.
Blog
Catch up on our latest insights on industry news and theories.
Webinars
Glossary
Click here for clarification on our terminology.
Help
FAQ
If you have a question about our tools, read here for our frequently asked questions.
Contact Us
Reach out to our team for support.
About MobileMoxie
Use Cases
Brands
Find out about the way brands use our tools to stay ahead of their competitors.
Agencies
Find out about how our tools help agencies win more business.
Analysts
Find out about how BI experts use our tools to tell a story with data.
Caching is the process of storing certain assets locally, so that they can be used again without require a full round trip request to the server. HTML, CSS, Images and JavaScript can all be cached. Caching is controlled by setting an expiry label, so that the browser knows how long an item can be stored an re-used, and when it should be fetched from the server freshly. Proper caching settings will speed up the load time for users, so Google recommends that webmasters set caching lifetimes for most static assets for one year. Using strong version control practices with your assets will also allow you to use long caching lifetimes, because if a file name changes, the server will automatically request the file from the server and not use the cached version. Not setting a caching lifetime tells the server that an asset must be fetched freshly each time and may not be cached at all. This often causes slow load times.
Related Terms: