Responsive Web Design
- Thread starter edefiners
- Start date
Now-a-days people prone towards smart phones, they browse everything online with their smart phones, hence a responsive website is more important so as to attract such mobile geeks towards your business.
Puneet Parmar
New Arrival
Hi ,
I think there is no disadvantage of responsive website design. Responsive web designing is the art of making a website available. Its advantage is the size of the web page, Images and words can change and automatically adjust to the size of a screen on any devices.
It Delivers a better user experience and helps you in decreasing bounce rate of a website. And the most important it helps a lot in search engine optimization.
I think there is no disadvantage of responsive website design. Responsive web designing is the art of making a website available. Its advantage is the size of the web page, Images and words can change and automatically adjust to the size of a screen on any devices.
It Delivers a better user experience and helps you in decreasing bounce rate of a website. And the most important it helps a lot in search engine optimization.
If the website is not responsive in its design, that means it will have a problem when it is accessed by a mobile browser. I have accessed some websites that give me tiny fonts and images because obviously it was designed for a computer monitor. There is also a website that I couldn't input anything. If you can check on Postloop.com with a tablet, you will see that it is not responsive although it is responsive when I use a smart phone.
Responsive vs. Adaptive
Firstly, there are two routes you can take with responsive design. Personally, I find the terminology to be misleading because they could both be two of the same to some, and to others, the complete opposite of each other. I feel people of either ideology are rightful in their thinking.
The first is responsive design itself; your website is truly responsive if you only use essential CSS declarations and simply let the layout work freely with the resolution it's given. Ems, rems and percentages are fluid units.
Adaptive design, on the other hand, means that you declare specific breakpoints for where CSS declarations change between resolutions and/or pixel densities. You can do this with @media queries. I personally opt for this method because it's nicer to work with.
Design Flexibility
As previously stated, the ideology behind responsive or adaptive web design is to cater for as great of an audience as you possibly can. In a world where the majority of users are accessing your websites via smartphone or tablet (mostly the former), you absolutely need to take into consideration the needs of those users who likely have some kind of metered connection to your website. A good website will always be designed with a 'mobile-first' philosophy so that you only send the absolute minimum amount of data to these users as possible. I've seen some sites with over 100 HTTP requests; that's how not to design your website.
Also, if your website is intended for business use, that should provide you with additional fuel to make sure it responds well to clients from all kinds of devices. Maximum exposure = larger profits.
Disadvantages
Pretty much the only possible disadvantage that I can think of right now is that producing a website that conforms to the responsive design philosophy simply isn't as straightforward as it otherwise would be to simply type out an HTML page and upload it. You do need to think about element placement and sizing, as well as the physical limitations of smaller and less powerful smartphones. A lot of JavaScript executions or CSS animations will hammer an older computer or low-end phone. You also need to consider the real estate of a smartphone screen, and then think about what a user might see 'above the fold'.
Were those proper requests or requests for ads? It's not unusual to have ads weighing in at 10 - 20MB on quite a few sites.
Mostly JavaScript junk and ads. Catastrophically optimized, and definitely not unusual.
Apparently, it's due to a thing called header bidding. Nasty stuff.
A good example of a ludicrous amount of HTTP requests, would be most game wiki-like websites.
GTA Wiki
192 requests
1.9 MiB transferred
Finish: 1.1 min
DOMContentLoaded: 2.72 s
Load: 5.73 s
Minecraft Wiki
245 requests
2.6 MiB transferred
Finish: 31.85 s
DOMContentLoaded: 2.93 s
Load: 20.16 s
🙄🙄🙄🙄🙄
GTA Wiki
192 requests
1.9 MiB transferred
Finish: 1.1 min
DOMContentLoaded: 2.72 s
Load: 5.73 s
Minecraft Wiki
245 requests
2.6 MiB transferred
Finish: 31.85 s
DOMContentLoaded: 2.93 s
Load: 20.16 s
🙄🙄🙄🙄🙄Affiliates
