When measuring our page speed, i.e. this https://tiket.hu/buyTicket/nagybojti-lelkinap-2021
Google show not this but our home page as rendered page. But we do not redirect. Then why?
Your site redirects to the home page on first visit.
If you then revisit the page it will stay on the correct page.
After a quick look around it appears that if you haven't already set "tempUserUuid" in local storage before you visit the page it redirects (as when I deleted this it redirected again).
This is probably why you haven't spotted the issue at your side.
As Page Speed Insights always runs from a clean cache (as if it was a first time visitor) this is why you are seeing this behaviour from PSI.
Related
Hi I'm having an issue with a site where visitors need to be members to access certain pages, but once logged in they go to these pages and still see the 'not logged in' page and need to refresh to view the actual content.
This obviously leads to a lot of bounces and I'd like to fix so that they see the content right away.
The root issue comes from some cache settings or something from the host - unfortunately we can't change host (and it's not a regular hosting company with a website but a design company reseller) for the time being. This issue does not occur in our offline environment of the same site.
I've already had to add a ?randomnumber to the stylesheet so it loads new versions properly. I was wondering if something like this would work - but dynamically as pages are being added all the time by different admins.
Or any other solutions also appreciated!
Thanks
Like you said, tweaking the caching settings would be the most ideal. But since that's not an option, I'd suggest adding a random, meaningless query string to the URL of the member pages so that it's seen as a 'new page' and (likely) won't cache.
So instead of /member-page
Direct them to /member-page?cache-buster=randomlyGeneratedStringHere
Working on a live Wordpress website deleted a page that has been published by mistake:
1- Turned the page into a Draft page, but it was still showing
2- Moved the page to Trash on the Wordpress dashboard and then deleted it permanently from the bin, but it still showing in the google search.
3-Cleared the catch, but it still showing up in google search and the link returns a 404 error.
Following up Google instruction:
Make removal permanent:
Remove or update the actual content from your site (images, pages,
directories) and make sure that your web server returns either a 404
(Not Found) or 410 (Gone) HTTP status code. Non-HTML files (like PDFs)
should be completely removed from your server. (Learn more about HTTP
status codes)
Block access to the content, for example by requiring a password.
Indicate that the page should not to be indexed using the noindex meta
tag. This is less secure than the other methods.The Remove URLs tool is
only a temporary
The first part is easy and shows the 404 error.
The second part:
Turning the page to a password protected page, now it takes me to password protected page and it is still showing on the Google search.
Also for noindex I had the following options:
Any idea why or any recommendation?
Thank you
Google search is based on indexing, it takes time to update your website's content, pages, and dependencies. Search updates are based on mechanism of Google crawlers (so called spiders). These spiders crawls your website's content and follow your meta tags and robots.txt file.
Generally, it will take about 1-3 days to get your page removed from the search results. There are no quick ways to do it as it is based on indexing. Make sure you update your Google webmasters account (just check for errors on your account which relates to a page not found).
one of my clients websites shows a wrong URL when I open the landing page in a new browser. Note that the source/ medium is organic. The sub pages that shows in my landing page column are right, but when I open it to see and check the website, it redirects me to a spammy website or what i believe is one of our competitors trying to copy our site. I have no idea how does it happen, i check all the property settings and everything is fine. Any suggestions?
Thanks!
Drupal 7.19
Acquia hosting
using Yottaa for optimization and monitoring
Problem: when trying to log in from home, we're experiencing something odd: we keep getting "logged out" ONLY on the front page. When you click anywhere inside the site, we get the admin toolbar and contextual links back. But we can't update the front page at all because it acts like it's logged out only for the front page.
This only happens when we're at home working on the site. This does not happen when we're in the work office.
Anyone experienced this? Don't know at what level is this occurring in...drupal, yottaa?
Found out the issue. It was a specific caching for the homepage on Yottaa's CDN. Once I turned this off, I was able to edit the home page again.
Note: They said that turning it off is not recommended. Instead, they recommend to flush the cache. Either way, found out what was causing the issue.
Folks,
I am working on an app that hosts certain pages from a different site in an iframe. Because the site is on a different network, I get prompted to log into their network in order to show the pages. All that is fine (the users of this site will be on the same network, so I'm not worrying about their logging in.)
However, on a different page, same app, I'm trying to do the same thing with a different set of pages from that same site. This time, I don't get prompted to log in, but do get the DNS Error page in the iFrame (I'm doing this in IE9, if it matters.) If I click "return to previous page" on the DNS Error page or right-click and click Back, the home page of the app (on the different network) appears in the iframe. After that, trying to load the desired page in the iframe works. But I'm baffled as to why and would prefer it load the first time I try it!
I'm guessing that the conjunction of the hosted pages being secure (HTTPS), their being on a different network, the iframe, and possibly also IE9 are somehow causing this. Anybody have any ideas?
Thanks,
Ann L.
If you go directly to the url that the iframe is pointing at do you get that same error or does it work? And make sure you go to the page the iframe is looking at and not what you think it is looking at. It may be that at some point in your process the page is generating the wrong url for the iframe.
The other thing is that it may be worth using fiddler to check your traffic to see if these other pages are trying to do some kind of redirect on you - they may be checking referrer and not liking connections from outside their network or similar.