That's right, this is more a description of how speculative execution works within modern processors (a quite familiar topic lately thanks to Meltdown, Spectre & co.).
... as it was said, the first brainfuck program prints xor-with-key. The second program doesn't output anything but it sets the memory "array" with 12 non-zero values. By XORing these values with the phrase present in the image (12 characters too) you get "35.205.32.11" which can be an IP (something in Google's ranges), geographical coordinates (interpreted as x,y they point somewhere in Israel, in fact) or I don't know whatever else.
I manage ads in several mobile apps and I've chosen to disable full screen video ads. Still Google's AdMob mail hints keep recommending to activate them as well in order to get more revenue. More revenue for me and more revenue for the ad provider, that's the only reason.
Being one of those that have no clue about tyres' sizes, I found the 205/45 17 combination after a few tries. It would be nice if the "tyres size choosing page" would retain your choices, after you get a "Size not found, please try again" or a "Please select Width, Profile and Size".
In the results page you may want to hide the table header's sorting buttons from the "Purchase column" and call the "back" button something like "New search" (this last point is quite debatable of course).
About the UI, it looks good overall (caveat: I have a bias toward non-distracting UIs). I don't really see the need for images.