Beeing a RESPONSIVE Theme does not mean, LOOKING similar in Phones and PC-Browsers.
All Content 'start's top left, therefore, depending on Browser/Phone Video-Resolution, really responsive
Themes will place, whatever comes after the VIEW-Limit reached, set by the Browser or Phone, will be added as NEXT LINE Content, until 'everything' is placed in correctly. If viewed with a 1024x768 Pixel Resolution View, a Page will look, as CREATED originally, but if viewed in a 800x400 Phone WIndow, or even less, it will look like a page with ugly vertical-step added and placed content only, if visual Design is NOT SPECIFICLY been 'worked on' to match today's Phone-Users Taste and Needs...
This, because the browser 'redirects', what cannot be placed behind the last 'block', but should, as originally designed, to the next following line. Even WORSE, if designed with FIXED Values, Phone Users may have to use cursors to manage to see the entire Page-width. Especially large sized images will eventually prevent Sections to 'shrink' to possibly Pre-Set 'width' settings. So you see, many thing have to be considered, to make it all work well.
As wider the Original View is designed, as longer a Phone Page (usually) will be, and a visual 1024x768 (or even higher) Design may possibly end up to look like a very long piece of visually disturbing garbage.
If one needs to design a Corporate Image 'reflecting' Shopping Place, I recommend, that two different 'Places' and URL's have to be built/used. As well as two Purpose-matching Themes designed. It's the second-easiest way to keep a certain 'Corp.ID-Face'. Or then, what I do, design an Openshop by Use of a 'Cursor-less Full View' 800x600 pixel max. Resolution Theme. Then, just about all Phones today are able to have a full width-view. This is the easiest way to keep a professional Look, regardless of the way they look at your Site, Visitors will see and can use it at it's best.
Just to give you a rough Idea...
A good Link to test Sizes:
It's not the Page-Width, what attracts Visitors, it's the 'usable' Content, in it...