It happens on Safari too. Chrome is Safari in a Google UI wrapper; performance, glitches, most of the web will function, appear, and crash the same on both.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
All iPads Real world performance: Snapdragon 800 vs Apple A7
- Thread starter macfacts
- Start date
- Sort by reaction score
It happens on Safari too. Chrome is Safari in a Google UI wrapper; performance, glitches, most of the web will function, appear, and crash the same on both.
That page is seriously jacked and not representative of the performance of any device. Even the Note performs horribly.
Edit: Scrolling by touching the middle of the page doesn't work, but scrolling by touching the far right side of the page works just fine.
Edit: Scrolling by touching the middle of the page doesn't work, but scrolling by touching the far right side of the page works just fine.
No it's most definitely not.
They both are based on WebKit but otherwise don't share code for the most part.
Unfair test, only Safari on iOS gets to use Nitro javascript.. Any non-safari based browsers are limited to the basic javascript engine..
Only good comparison is Safari vs. any Android browser.
Only good comparison is Safari vs. any Android browser.
Errrr ... no.
Safari doesn't use the same things on iOS that Chrome does. No browser is allowed to use the same things that Safari does.
Yes they most certainly are. Most things, actually, except for Nitro because that has low-level, unprotected hardware access.
I thought that Safari also was given access to more RAM, a hack that Apple uses to make Safari faster?
Actually, they argue that most Android apps are formatted for smartphone screens, and are often just blown-up versions on tablets. This is still often the case.
What a user sees when going to a website is entirely up to the developers of that site. Good developers will find a way to make their interface work well, with a unified look, on at least tablet and desktop platforms, if not tablet, desktop AND smartphone screens. Fair-to-middling developers will try to do tablet/mobile specific views, but will give you a choice to go to the desktop version.
Only really bad web developers will force users to a certain view, and not give them any choice in the matter. Guess which type of web devs the ABC News site likely has.
There are plenty of other webpages that show the full desktop site in both Safari and Chrome, and can be used as comparisons. nytimes.com is one of them. news.google.com is another. freep.com, nbcnews.com, cbsnews.com, foxnews.com... just a few sites with similar genres and subject matter that can be be used as appropriate web browser performance comparisons, for real-world usage.
All you've demonstrated here is that the ABC News website in particular is slower in the iOS version of Chrome. That alone doesn't lead to a logical conclusion that the CPU must be slower. Everything from the site code, to difference in app code, can all be factors.
However, if you're trying to use this is justification for keeping your Note 3, just stop. Return your iPad Air, and enjoy your Note 3. There should be no need at all for you to jury-rig tests to convince yourself of something you want to be true. Just use your tablet of choice and be happy.
Why people need to spend so much time convincing other people that their tablet goes so much faster than everyone else's, I'll never get. Does your tablet work for YOU? Yes? Hooray!
No? Well, sorry to hear that. Go get another one.
Last edited:
When sites default to the mobile version, it's not the browser doing it. The browser simply identifies itself as a mobile browser (ipad, iphone, safari version x etc...) and the website switches to mobile. If the website is properly designed, it will switch to mobile for phones, but stay with the regular site for tablets. That being said, most sites have a link at the bottom of the page (abcnews.com included) that toggles between the full site and the mobile site.
Something is horribly wrong with abcnews.com, however. There might be some kind of funky java ad overlay that doesn't get properly processed on mobile browsers (iOS and Android), thus blocks/hampers interactions in the middle of the page (scrolling on the far right edge of the page seems to bypass this).
I jail broke my devices and installed an app that allows browsers to use java script..Didn't notice a difference one bit.
It's likely not. If you actually do side by side speed tests and time it, it shouldn't be much quicker if it's even quicker at all.
The site works perfectly fine on my iPad air (safari), or am I doing something wrong
EDIT:
Tried it with chrome and it still works (although not ultra smooth like safari)
The site works perfectly fine on my iPad air (safari), or am I doing something wrong
EDIT:
Tried it with chrome and it still works (although not ultra smooth like safari)
How did you display the desktop version of that page in safari?
It displayed the mobile version at first, but when I tapped on "desktop version". The desktop version was displayed. The next time I went to this page it automatically loaded desktop version.
Having said that, I've tried again and it's broken (I didn't go to that specific article the first time). It's not due to A7 chip or whatever. The site (or only that specific article) is poorly done (for whatever reason). Every other site works perfectly smooth and ultra fast on my Air.
I'm not trying to troll you, but what is wrong with the linked site? The "regular version" loads up just fine for me on Chrome and scrolls just fine. iPad Air here.
I don't use Safari.
Edit: When you select "regular version" it takes you to ANOTHER page which DOES work ok. However the Zimmerman article page (if you now load it up) is totally unusable and crash inducing in both Chrome and Safari. I gotta say "poorly coded page" is a ****** excuse for what really is a terrible memory management problem in Apple's software.
I don't use Safari.
Edit: When you select "regular version" it takes you to ANOTHER page which DOES work ok. However the Zimmerman article page (if you now load it up) is totally unusable and crash inducing in both Chrome and Safari. I gotta say "poorly coded page" is a ****** excuse for what really is a terrible memory management problem in Apple's software.
Last edited:
You can see in his video that even the Android device has problems with this particular page, so it's not a "terrible memory management problem in Apple's software." In addition to that, if you scroll along the far right edge of the screen on that page, scrolling works just fine, as long as you avoid interacting with certain elements. It's the page, not the device.
Last edited:
Actually now that I've examined the page a bit closer the problem seems to be a single element: the scrolling picture widget linking to other articles. As long as it's not on the screen scrolling even in Chrome (on iOS) is pretty smooth.
What I wouldn't give for AdBlock on iOS..