hey guys i am having a problem that i see others with online but i am yet to find a fix for my website.
facebook not detecting my images as of a couple of hours ago, i tried disabling hotlinks in cloudflare, tried fb debuger and scrapping tool etc no solution.
example if you try to share this page, no picture appears: http://www.yardhype.com/12-year-old-jamaican-girl-wins-master-chef-junior-competition/
ERROR message
"Provided og:image URL, ........testsite/wblob/5433A6CF57A599/2803/3DF62/w3l6_ERf2C3ADvxqhgccQg/jasmin.png could not be downloaded because it exceeded the maximum allowed sized of 8Mb."
the image is not over 8mb
ALso correct url is shown in the raw tag area
When I opened that link http://www.yardhype.com/12-year-old-jamaican-girl-wins-master-chef-junior-competition/ I don't see the image regardless; I opened up Chrome's debugger and saw this:
A Parser-blocking, cross site (i.e. different eTLD+1) script,
http://ajax.cloudflare.com/cdn-cgi/nexp/dok3v=85b614c0f6/cloudflare.min.js,
is invoked via document.write. The network request for this script MAY be
blocked by the browser in this or a future page load due to poor network
connectivity. If blocked in this page load, it will be confirmed in a
subsequent console message.See
https://www.chromestatus.com/feature/5718547946799104 for more details.
So the way that page is displaying the image is likely not up to standards.
Related
So I just linked my custom domain with firebase and it shows connected:
image of connected status
which is great. But now when I search website without /index.html, it redirects me to this page. I want to see this page which is accessible only when I append website domain with /index.html. I am new to firebase. How can I make my domain access index.html page without specifically mentioning /index.html?
EDIT: I just noticed that it's working fine on the mobile devices and in the incognito tab on PC. It must be something with my chrome browser I am logged in with. which is weird :/ should I change the title? Cause I think fault could be related to browser. but help me if you can.
So the real issue wasn't the configuration but the browser cache. if you are facing similar issues then try clearing the browser cache or try browsing the website on a different device. Spent literally 1-2 hrs on such a silly problem. Either way, thank you.
My problem is as illustrated in the above picture, where we can see a set of two font files being fetched and transferred twice.
These fonts are self-hosted for my Gatsby.js site, and this double-fetching leads me to see font flashes twice on page load. Some clues that might shed some light:
1) Lighthouse is complaining about this error being logged into the console:
"Failed to load resource: net::ERR_ACCESS_DENIED" with regards to one of the fonts (Open Sans).
2) The initiator for the second set of font requests is "other". A google search tells me that "other" refers to requests made from a user (which seems unlikely here since this is on page load) or for preloaded requests (I didn't explicitly include a preloaded link in my HTML head, but maybe one of those Webpack scripts?).
3) This issue only appears in my production build. It works okay and only fetches once in development mode.
Does anyone have any idea what might be causing this, or could perhaps give me some advice as to how I might even begin to debug this problem?
It tried to use HTTPS with og:image but the image is blank with Facebook Share
safe_image.php returns this error (x-error-detail) :
x-error-detail CDN request for an invalid safe image:
I have no error on the Facebook debug tools.
Any advice ?
Here's a checklist that might or might not help you with it:
Is the content behind Basic Auth?
Is the content inaccessible by Facebook crawlers because of robots.txt? More info
Is the site on a VPN or is it publicly available?
As #CBroe suggested, try running the image URL directly into the scraper, and just in case click Scrape again. Once you see the image being crawled properly there, there's no guarantee Scrape Again on the page that was using it as og:image will get fixed. This happened to me... My hard guess, it's a load balancing issue between their image crawlers (safe_image.php)
Edit: I fixed my case by realizing I was missing a tag. Yes. Missing a tag on a og:type video, and Facebook was just removing the thumbnail instead of saying "missing a tag bruh"
Make sure you see all the following 5 properties in the debug tool for og:video:
url
secure_url
type
width
height
Upon loading my site (https://ameersavage.com), certain images do not load in Chrome. Upon reloading the page, the results vary. Rarely does everything load properly in Chrome. This only started happening once I uploaded the site to the server.
When I uploaded the site using the server's online cPanel, none of the assets appeared until I started fiddling with each individual file's permission. I then tried uploading the site using FTP (Transmit) which produced far better results, but still certain assets sometimes do not always show up once the page loads.
Do you think this is a reflection of poor server performance? I wanted to get a second opinion before I subscribe to a new server provider (any recommendations?).
So, there's this blog I visit often, and it has a lot of pictures.
But the thing is, they are all broken. The image is there, and I found that if I use a proxy server and access the blog, some pictures are there. Some are still broken, so then I have to right click the broken image, copy the image URL, open the URL in a different tab/windows, and once that picture finishes loading, I refresh the blog, and the picture I loaded on a different windows now shows....
Does anyone know why this happens, and how I can get it fixed?? Thanks.
In case you don't understand what I mean, This is the blog that makes this happen
http://wersierre.tumblr.com/
This applies to Firefox, chrome, IE in my case.
This is very likely to be the case that the target server is configured to prevent hotlinking. When accessing the images via the page you posted, the HTTP response code of the images is 403, it indicates the server can be reached and understood the HTTP request, but refuses to take any further action.