will my website work on mobile devices?
absolutely. your website will look great on mobile devices. we don’t charge extra for this. it comes as standard.
You **DON'T** create two versions of your navigation! I told you (in one of your other four threads regarding this same issue) that you have to **REPLACE** the markup (HTML) from your current navigation with the navbar markup that comes with Bootstrap out of the box. The classes on that Bootsrap navbar will handle the responsiveness for your mobile nav. The only thing that you have to to do is change the default design of the navbar to that of your current navigation.


Check these two Bootsrap navbar examples.  

<https://bootsnipp.com/snippets/Oe7QM>  

The first is the **default** and the second the **inverse** version. The mobile version of the navigation is baked in the Bootstrap CSS file (which you load twice by the way on <http://www.purelineliving.com/> - Get rid of one!!!). You don't have to do much else!


You use Bootstrap so **STICK** to the HTML (markup) & CSS (classes) of the framework and certainly if you don't have any clue what you're doing.  

<https://getbootstrap.com/docs/4.0/getting-started/introduction/>


I also mentioned before that you have horizontal scrollbars on tablet and mobile screens, because your images are not responsive. They have all defined width and height attributes in the markup, so they won't shrink once the screen gets smaller. hi roland, the universal gui will ultimately become a fully-fledged alternative to the windows, web and mobile user interfaces. we will make sure that current layouts (with tabs and inline details) in windows and web are also supported in the universal gui, to make the transition as smooth as possible! hi there,

you should set every “height” to “auto”.

the “height” in your designer tool isn’t the same as a mobile phone. your elements in the blocks with a set height are probably bigger than the set height you used.

hope this works!

cheers,

max zijlstra links to a phone layout should have /phone in the code... I would assume you copy | pasted these links from your desktop layout and that of course makes them go there in stead but the good news is its easy to fixp.s, you did the right thing and its nice to see a designer do basic testing of their site How a. ch said I have also seen this with insufficient memory issues and also packages that were left with the same package id and even if the graphics need to be resized. What was said:


If you [support multiple screens](https://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=) , I would make sure there are graphics in each MDPI, HDPI, XHDPI respectively and that they are [optimized](https://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=) and set to the [appropriate DPI](https://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=) . This should ensure that all devices and API levels play well.



  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

Even if that isn't the root of your problem, it's good to keep an eye on efficiency and reliability. <p>hi</p>
<p>from an seo perspective there are no risks in taking this approach, but you will be limiting your overall visibility in local markets because googlebot will only see the english version of your content. it will not see any of the translated versions at all and therefore you will struggle to rank in your local markets such as spain, france, india etc.</p>
<p>in order to take full advantage of available local search volume you'll need to set up separate urls with fully translated content (do not use google translate!) for your target markets.&nbsp;</p>
<p>but in the meantime, no it's not bad for seo (in so far as there are no risks), but it is not beneficial.</p>
<p>hope this helps and good luck!</p> hey [@rapha](/u/rapha) , could you try these changes on your mobile mode? this suggestion stems from the fact that your cart takes up the whole height and is really narrow.

[[image]](https://aws1.discourse-cdn.com/business5/uploads/webflow1/original/3x/c/1/c183e24cd6648f19454eddfe3bf89087e1edfa29.png "image")

the result i get is the following:

[[image]](https://aws1.discourse-cdn.com/business5/uploads/webflow1/original/3x/3/3/338e06df505307c5fdd1c817a2ba847bf9848d88.jpeg "image")

the height of the cart in px is not recommended personally, i would use either % v… we believe this issue has been fixed with our most recent release, version 10.9.
 


 you can learn more here:
 



 please try updating, and let me know if you have any other questions.
 


  
 


 also, if you are experiencing this issue via the web client, please let us know here: Have you tried restarting your browser? You are using position:absolute; Don't, it usually leads to endless problems.



Even if you had a real need to use it, why are you placing things at left 1400px!!!



This is right on the edge of the average monitor - how large is your monitor? I work with my browser open at a width of about 1000-1200px (note I didn't mention the size of my monitor). The main reason people have big monitors is so they can have two windows open next to each other, not so that they can run a browser window open at 2800px wide.



I suggest you start by looking at ordinary websites and studying the css. you'll discover that many sites use a wrapper div with a fixed width, while others use a wrapper div with a percentage width and a max-width, to prevent ending up with a huge long line of text 2500px long for example. Then they center the div using margin:auto. That gets the content in the middle of the page on the vast majority of screens, and browser viewports.



Don't lay out a screen using position:absolute. You are not painting pretty pictures on a screen, you should be using html and css to control the layout and check how the layout looks every time, by resizing the window looking for errors.



Also, a contact form needs the input boxes to be part of a <form>, so you'll have to read up on how they work. And a form needs an action, so you'll have to learn a bit about scripting, probably php.