by
Oxypage.com
0 (0 reviews)
OXP Mobile First Toolkit
Ten fixes and additions for the things that break on phones and that your theme or page builder does not give you a switch for.
OXP Mobile First Toolkit ranks #72,996 among WordPress.org plugins with 0+ active installations, and was last updated Oct 12, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.1.1
Current Version v1.1.1
Updated 2 weeks ago
Last Update on 12 Oct, 2026
Refreshed 2 days ago
Last Refreshed on
Actively maintained
Rank
#72,996
—
No change
Active Installs
0+
-100%
KW Avg Position
45
—
No change
Downloads
201
+2 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
45,428
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 10 more installs to reach 10+
Rank Changes
Current
#72,996
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.1.1
- Last Updated
- Oct 12, 2026
- Requires WP
- 6.7+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- Oxypage.com
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about OXP Mobile First Toolkit
On a desktop it does nothing at all: no requests are made, apart from the overflow report for a logged-in administrator. On a phone it loads a small runtime plus only the modules you switched on, with no dependencies and no framework. Two of them, the iOS input zoom and the vertical fade, are a few lines of CSS printed straight into the page and load nothing at all.
No. Every module that changes how a page renders is gated behind (hover: none) and (pointer: coarse), in the script that decides what to load and again in the CSS. The overflow report is the one thing that also appears on a desktop, and only for a logged-in administrator: it draws a panel over your own page and changes nothing about the page itself. I already use OXP Mobile Fixed Background. Keep it. The toolkit detects it and stands down from that one module, so the two never fight. Deactivate it if you would rather manage fixed backgrounds from the toolkit instead. The hover module is activating far too many things. That is its default: with nothing configured it activates every element on the page that has a hover effect, because the alternative is a module that does nothing until you write a CSS selector. "Only these elements" is how you narrow it: give it a selector such as .card, .tile and the automatic detection switches off entirely, so only what you named is touched. The paid build adds the other way round, leaving a named region alone and ignoring anything under a width you set. The hover module does not activate one of my effects. Almost certainly the effect is defined in a stylesheet served from another domain, such as a CDN. Browsers refuse to let any script read the rules of a cross-origin stylesheet, so the plugin cannot find that rule to mirror it. Serving the stylesheet from your own domain fixes it.
No. It is rendered only for logged-in users who can manage options. The overflow report used to list something and now it does not. It now ignores any element whose overflow a container already clips or scrolls, because that element cannot make the page drag sideways and listing it was listing a solved problem. If you dismissed it instead, the panel says how many are hidden and offers to show them again; dismissals are remembered per page, in your own browser.
No, and it cannot. No browser on iOS has ever implemented the Vibration API, Chrome and Firefox for iPhone included, since both are Safari underneath. It works on Android in Chrome, Firefox and Samsung Internet. That is why it is off by default and labelled. The settings screen uses a word I do not know. Then it is set to the wrong voice for you. At the top of the page there is a bar with three choices: plain, hybrid and technical. Plain never uses a technical term at all. It only changes the words on that screen, so switching between them is free and changes nothing about your site. I typed a description into "Only these elements" and nothing happened. That box wants a CSS selector, which is the name a designer gave the element and usually starts with a dot, like .card. A description of the element, however accurate, matches nothing. The plugin now says so when you save something that does not look like a selector. If you do not know the name, leave the box empty: the module finds the elements on its own, which is what it is designed to do.
Not in this build: it shows on every page. Choosing pages for it to stay away from is one of the things the paid build adds, and it is worth knowing about either way, because a fixed bar sitting on top of a Place order button is the most expensive thing this module can do. If you are on the free build and the bar is in the way on one page, leave the module switched off on that site until you are sure it is not.
No. Every module here is complete and runs with no key, no trial and no time limit. The paid build is a separate plugin, sold on our own site, and none of its code is included in this one: what you see on a module's card where its paid controls would be is a description of them, not a control that refuses to work.
You do not install it over this one by hand. Buying gives you the paid build as its own download, along with a licence key you activate from the plugin's own menu entry, and it replaces this plugin. Your settings are in one option row and are left exactly as they are, so everything you configured here is still configured afterwards.