Crawl report shows that it gets 4xx errors for pages that work fine. Why?

[TeamViviRealEstate]

On the crawl report it has all these "Critical Crawler Issues". They all say "4xx Error", yet when i click on the link from the crawler report, it goes to a perfectly functioning page, not a 404 page or anything. If i click in it actually says it's a 403 error. It's all for pages generated by the IDX solution for our real estate website.

Is Moz broken or am i missing something?

Here are a couple examples:

<dl class="crawl-page-details-list">

<dd class="crawl-page-details-list-emphasis">https://teamvivi.com/homes-for-sale-map-search/</dd>

<dd class="crawl-page-details-list-emphasis">

<dl class="crawl-page-details-list">

<dd class="crawl-page-details-list-emphasis">https://teamvivi.com/email-alerts/</dd>

</dl>

</dd>

</dl>

[WebElaine]

There are definitely other optimizations you can do, and Visual Composer may not be the biggest slowdown. I just noticed when I viewed the source code that it was inserting a lot of separate CSS files and so it may be contributing some. Other optimizations like going through PageSpeed Insights' recommendations may get you farther.

But any themes and plugins you use on a WP site, those resources are loaded across the whole site - even on pages they're not used on. So in a lot of cases, selecting a premade theme or having one built from scratch can make your site a lot faster than using page builders. Basically it's a tradeoff: do you want to pay someone to code a theme specifically for you and do the heavy lifting up front (or make design compromises and use a well-coded prebuilt theme), so the code that renders to visitors is lightweight; or do you want to just go wysiwyg on the admin side, so the code that renders to visitors is bogged down but you don't have to hire a developer?

[TeamViviRealEstate]

Ugh, that's not good news since my entire site is built with Visual Composer basically.... Interestingly though, those pages are not even using Visual Composer. Those are pages that are generated by the IDX solution (iHomeFinder by Optima Express).

[WebElaine]

A 403 error means the crawler isn't being allowed to access that page. You should check robots.txt and if nothing is blocking there, check with your host to see if they can help identify why Roger is being blocked from those particular pages.

Related question: https://moz.com/community/q/403-error-code-but-page-shows-no-error

On a side note, those pages took a really long time to load for me, so I'd also look into site speed. Visual Composer for one is adding all sorts of different stylesheets and bogging things down.