Should I bother with AMP if my website is lighter?
Clash Royale CLAN TAG#URR8PPP
I have a webpage with almost only static content that weight a compressed size of 25ko.
Should I bother with AMP for pure SEO reasons ? I could very easily opt-in for AMP since the page is AMP-compliant. But the AMP scripts itself adds quite a weight to the page.
Is there any thing I'm missing about AMP aside from a big javascript restriction from a javascript file ?
seo amp
add a comment |
I have a webpage with almost only static content that weight a compressed size of 25ko.
Should I bother with AMP for pure SEO reasons ? I could very easily opt-in for AMP since the page is AMP-compliant. But the AMP scripts itself adds quite a weight to the page.
Is there any thing I'm missing about AMP aside from a big javascript restriction from a javascript file ?
seo amp
1
The real purpose of AMP isn't to create small pages. AMP pages are smallish and static, yes, but that isn't why Google pushes it. The purpose of AMP is to allow Google to use your content.
– Stephen Ostermiller♦
Feb 2 at 12:42
add a comment |
I have a webpage with almost only static content that weight a compressed size of 25ko.
Should I bother with AMP for pure SEO reasons ? I could very easily opt-in for AMP since the page is AMP-compliant. But the AMP scripts itself adds quite a weight to the page.
Is there any thing I'm missing about AMP aside from a big javascript restriction from a javascript file ?
seo amp
I have a webpage with almost only static content that weight a compressed size of 25ko.
Should I bother with AMP for pure SEO reasons ? I could very easily opt-in for AMP since the page is AMP-compliant. But the AMP scripts itself adds quite a weight to the page.
Is there any thing I'm missing about AMP aside from a big javascript restriction from a javascript file ?
seo amp
seo amp
edited Feb 2 at 8:46
Ado Ren
asked Feb 2 at 8:17
Ado RenAdo Ren
354
354
1
The real purpose of AMP isn't to create small pages. AMP pages are smallish and static, yes, but that isn't why Google pushes it. The purpose of AMP is to allow Google to use your content.
– Stephen Ostermiller♦
Feb 2 at 12:42
add a comment |
1
The real purpose of AMP isn't to create small pages. AMP pages are smallish and static, yes, but that isn't why Google pushes it. The purpose of AMP is to allow Google to use your content.
– Stephen Ostermiller♦
Feb 2 at 12:42
1
1
The real purpose of AMP isn't to create small pages. AMP pages are smallish and static, yes, but that isn't why Google pushes it. The purpose of AMP is to allow Google to use your content.
– Stephen Ostermiller♦
Feb 2 at 12:42
The real purpose of AMP isn't to create small pages. AMP pages are smallish and static, yes, but that isn't why Google pushes it. The purpose of AMP is to allow Google to use your content.
– Stephen Ostermiller♦
Feb 2 at 12:42
add a comment |
2 Answers
2
active
oldest
votes
I just compared two html pages that I created recently. The filesize of the AMPed version is 20 percent larger than the regular page because of the added css/script calls. This, of course, does not include the actual JS the AMPed page requires.
Nobody hates AMPed pages more than I do; Google has pushed this nonsense on us. I say we all use responsive design. The Google Way is to create redundant copies of every single page.
Should you use AMP? Well -- yes, you must if you want to rank on Google. Around 60 percent of searches are being performed on mobile devices. I can understand ranking mobile-friendly sites higher, but the AMPed method is Google tomfoolery. To answer your question: no, you are not missing anything.
Paradoxically, the AMPed version loads in 0.488s and the regular page, 0.7s. This was based upon one test from gtmetrix.com.
1
Some articles online show AMP pages are actually slower in certain conditions but my complaint is giving the wheel to Google to manage delivery of your web site. What happens should that all goes wrong. Eventually, everything goes all wrong.
– Rob
Feb 2 at 12:27
add a comment |
I did not agree with above answer that you should use AMP if you want to rank for mobile query. I've mobile responsive site, and it drives good traffic on it without AMP.
AMP just block other javascript to render and force you to minimize(or use their own) CSS codes, so your webpage load fast. Another thing is that they even store your site on their own server, it means they don't serve results from your live site, they use their own cache version to show it. So it slightly boost your webpage speed, because it now directly serve from Google cache. Other than that, I don't see any real impact of AMP version.
If you know what AMP does, and if you can do the same with your own site, then you don't require AMP at all. I've static website, which doesn't have any javascript other than Async AdSense codes, and I use internal CSS, so if I try to add AMP on it, then it will add 2-3 more seconds on it. AMP is directly related to speed, so Google use pagespeed as ranking factor without judging what technology you're using.
You can see John Mueller tweet as well
AMP isn't a ranking factor; if you decide to disable it, make sure to
redirect appropriately.
And here is my search console data about position. It's all rank good without AMP.
And here is my search console data about devices.
As you can see my majority traffic is coming from mobile searches.
I agree with some specific case like news article where AMP help you to rank on top, because they show carousel stories with rich snippet. But it doesn't apply on all mobile query.
1
Thanks, didn't notice the ranking factor mention. Well let's hope it doesn't change is a near future.
– Ado Ren
Feb 3 at 8:40
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "45"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f120677%2fshould-i-bother-with-amp-if-my-website-is-lighter%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I just compared two html pages that I created recently. The filesize of the AMPed version is 20 percent larger than the regular page because of the added css/script calls. This, of course, does not include the actual JS the AMPed page requires.
Nobody hates AMPed pages more than I do; Google has pushed this nonsense on us. I say we all use responsive design. The Google Way is to create redundant copies of every single page.
Should you use AMP? Well -- yes, you must if you want to rank on Google. Around 60 percent of searches are being performed on mobile devices. I can understand ranking mobile-friendly sites higher, but the AMPed method is Google tomfoolery. To answer your question: no, you are not missing anything.
Paradoxically, the AMPed version loads in 0.488s and the regular page, 0.7s. This was based upon one test from gtmetrix.com.
1
Some articles online show AMP pages are actually slower in certain conditions but my complaint is giving the wheel to Google to manage delivery of your web site. What happens should that all goes wrong. Eventually, everything goes all wrong.
– Rob
Feb 2 at 12:27
add a comment |
I just compared two html pages that I created recently. The filesize of the AMPed version is 20 percent larger than the regular page because of the added css/script calls. This, of course, does not include the actual JS the AMPed page requires.
Nobody hates AMPed pages more than I do; Google has pushed this nonsense on us. I say we all use responsive design. The Google Way is to create redundant copies of every single page.
Should you use AMP? Well -- yes, you must if you want to rank on Google. Around 60 percent of searches are being performed on mobile devices. I can understand ranking mobile-friendly sites higher, but the AMPed method is Google tomfoolery. To answer your question: no, you are not missing anything.
Paradoxically, the AMPed version loads in 0.488s and the regular page, 0.7s. This was based upon one test from gtmetrix.com.
1
Some articles online show AMP pages are actually slower in certain conditions but my complaint is giving the wheel to Google to manage delivery of your web site. What happens should that all goes wrong. Eventually, everything goes all wrong.
– Rob
Feb 2 at 12:27
add a comment |
I just compared two html pages that I created recently. The filesize of the AMPed version is 20 percent larger than the regular page because of the added css/script calls. This, of course, does not include the actual JS the AMPed page requires.
Nobody hates AMPed pages more than I do; Google has pushed this nonsense on us. I say we all use responsive design. The Google Way is to create redundant copies of every single page.
Should you use AMP? Well -- yes, you must if you want to rank on Google. Around 60 percent of searches are being performed on mobile devices. I can understand ranking mobile-friendly sites higher, but the AMPed method is Google tomfoolery. To answer your question: no, you are not missing anything.
Paradoxically, the AMPed version loads in 0.488s and the regular page, 0.7s. This was based upon one test from gtmetrix.com.
I just compared two html pages that I created recently. The filesize of the AMPed version is 20 percent larger than the regular page because of the added css/script calls. This, of course, does not include the actual JS the AMPed page requires.
Nobody hates AMPed pages more than I do; Google has pushed this nonsense on us. I say we all use responsive design. The Google Way is to create redundant copies of every single page.
Should you use AMP? Well -- yes, you must if you want to rank on Google. Around 60 percent of searches are being performed on mobile devices. I can understand ranking mobile-friendly sites higher, but the AMPed method is Google tomfoolery. To answer your question: no, you are not missing anything.
Paradoxically, the AMPed version loads in 0.488s and the regular page, 0.7s. This was based upon one test from gtmetrix.com.
edited Feb 3 at 2:19
answered Feb 2 at 11:00
Keith TysingerKeith Tysinger
14018
14018
1
Some articles online show AMP pages are actually slower in certain conditions but my complaint is giving the wheel to Google to manage delivery of your web site. What happens should that all goes wrong. Eventually, everything goes all wrong.
– Rob
Feb 2 at 12:27
add a comment |
1
Some articles online show AMP pages are actually slower in certain conditions but my complaint is giving the wheel to Google to manage delivery of your web site. What happens should that all goes wrong. Eventually, everything goes all wrong.
– Rob
Feb 2 at 12:27
1
1
Some articles online show AMP pages are actually slower in certain conditions but my complaint is giving the wheel to Google to manage delivery of your web site. What happens should that all goes wrong. Eventually, everything goes all wrong.
– Rob
Feb 2 at 12:27
Some articles online show AMP pages are actually slower in certain conditions but my complaint is giving the wheel to Google to manage delivery of your web site. What happens should that all goes wrong. Eventually, everything goes all wrong.
– Rob
Feb 2 at 12:27
add a comment |
I did not agree with above answer that you should use AMP if you want to rank for mobile query. I've mobile responsive site, and it drives good traffic on it without AMP.
AMP just block other javascript to render and force you to minimize(or use their own) CSS codes, so your webpage load fast. Another thing is that they even store your site on their own server, it means they don't serve results from your live site, they use their own cache version to show it. So it slightly boost your webpage speed, because it now directly serve from Google cache. Other than that, I don't see any real impact of AMP version.
If you know what AMP does, and if you can do the same with your own site, then you don't require AMP at all. I've static website, which doesn't have any javascript other than Async AdSense codes, and I use internal CSS, so if I try to add AMP on it, then it will add 2-3 more seconds on it. AMP is directly related to speed, so Google use pagespeed as ranking factor without judging what technology you're using.
You can see John Mueller tweet as well
AMP isn't a ranking factor; if you decide to disable it, make sure to
redirect appropriately.
And here is my search console data about position. It's all rank good without AMP.
And here is my search console data about devices.
As you can see my majority traffic is coming from mobile searches.
I agree with some specific case like news article where AMP help you to rank on top, because they show carousel stories with rich snippet. But it doesn't apply on all mobile query.
1
Thanks, didn't notice the ranking factor mention. Well let's hope it doesn't change is a near future.
– Ado Ren
Feb 3 at 8:40
add a comment |
I did not agree with above answer that you should use AMP if you want to rank for mobile query. I've mobile responsive site, and it drives good traffic on it without AMP.
AMP just block other javascript to render and force you to minimize(or use their own) CSS codes, so your webpage load fast. Another thing is that they even store your site on their own server, it means they don't serve results from your live site, they use their own cache version to show it. So it slightly boost your webpage speed, because it now directly serve from Google cache. Other than that, I don't see any real impact of AMP version.
If you know what AMP does, and if you can do the same with your own site, then you don't require AMP at all. I've static website, which doesn't have any javascript other than Async AdSense codes, and I use internal CSS, so if I try to add AMP on it, then it will add 2-3 more seconds on it. AMP is directly related to speed, so Google use pagespeed as ranking factor without judging what technology you're using.
You can see John Mueller tweet as well
AMP isn't a ranking factor; if you decide to disable it, make sure to
redirect appropriately.
And here is my search console data about position. It's all rank good without AMP.
And here is my search console data about devices.
As you can see my majority traffic is coming from mobile searches.
I agree with some specific case like news article where AMP help you to rank on top, because they show carousel stories with rich snippet. But it doesn't apply on all mobile query.
1
Thanks, didn't notice the ranking factor mention. Well let's hope it doesn't change is a near future.
– Ado Ren
Feb 3 at 8:40
add a comment |
I did not agree with above answer that you should use AMP if you want to rank for mobile query. I've mobile responsive site, and it drives good traffic on it without AMP.
AMP just block other javascript to render and force you to minimize(or use their own) CSS codes, so your webpage load fast. Another thing is that they even store your site on their own server, it means they don't serve results from your live site, they use their own cache version to show it. So it slightly boost your webpage speed, because it now directly serve from Google cache. Other than that, I don't see any real impact of AMP version.
If you know what AMP does, and if you can do the same with your own site, then you don't require AMP at all. I've static website, which doesn't have any javascript other than Async AdSense codes, and I use internal CSS, so if I try to add AMP on it, then it will add 2-3 more seconds on it. AMP is directly related to speed, so Google use pagespeed as ranking factor without judging what technology you're using.
You can see John Mueller tweet as well
AMP isn't a ranking factor; if you decide to disable it, make sure to
redirect appropriately.
And here is my search console data about position. It's all rank good without AMP.
And here is my search console data about devices.
As you can see my majority traffic is coming from mobile searches.
I agree with some specific case like news article where AMP help you to rank on top, because they show carousel stories with rich snippet. But it doesn't apply on all mobile query.
I did not agree with above answer that you should use AMP if you want to rank for mobile query. I've mobile responsive site, and it drives good traffic on it without AMP.
AMP just block other javascript to render and force you to minimize(or use their own) CSS codes, so your webpage load fast. Another thing is that they even store your site on their own server, it means they don't serve results from your live site, they use their own cache version to show it. So it slightly boost your webpage speed, because it now directly serve from Google cache. Other than that, I don't see any real impact of AMP version.
If you know what AMP does, and if you can do the same with your own site, then you don't require AMP at all. I've static website, which doesn't have any javascript other than Async AdSense codes, and I use internal CSS, so if I try to add AMP on it, then it will add 2-3 more seconds on it. AMP is directly related to speed, so Google use pagespeed as ranking factor without judging what technology you're using.
You can see John Mueller tweet as well
AMP isn't a ranking factor; if you decide to disable it, make sure to
redirect appropriately.
And here is my search console data about position. It's all rank good without AMP.
And here is my search console data about devices.
As you can see my majority traffic is coming from mobile searches.
I agree with some specific case like news article where AMP help you to rank on top, because they show carousel stories with rich snippet. But it doesn't apply on all mobile query.
answered Feb 3 at 4:42
GoylloGoyllo
4,9761516
4,9761516
1
Thanks, didn't notice the ranking factor mention. Well let's hope it doesn't change is a near future.
– Ado Ren
Feb 3 at 8:40
add a comment |
1
Thanks, didn't notice the ranking factor mention. Well let's hope it doesn't change is a near future.
– Ado Ren
Feb 3 at 8:40
1
1
Thanks, didn't notice the ranking factor mention. Well let's hope it doesn't change is a near future.
– Ado Ren
Feb 3 at 8:40
Thanks, didn't notice the ranking factor mention. Well let's hope it doesn't change is a near future.
– Ado Ren
Feb 3 at 8:40
add a comment |
Thanks for contributing an answer to Webmasters Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f120677%2fshould-i-bother-with-amp-if-my-website-is-lighter%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
The real purpose of AMP isn't to create small pages. AMP pages are smallish and static, yes, but that isn't why Google pushes it. The purpose of AMP is to allow Google to use your content.
– Stephen Ostermiller♦
Feb 2 at 12:42