Introduction#
Free Space Application and Simple Testing (1) – ACEVS
Free Space Application and Simple Testing (2) – ACEVS
Free Space Application and Simple Testing (3) – ACEVS
Free Space Application and Simple Testing (4) – ACEVS
After applying for a few, I didn't tinker much and found the built-in testing tool in Chrome. Just for fun, testing a bit.
Simple Testing#
Last time it was just visual inspection, without any tools; this time I have a tool.
I will also test the previously successfully registered free spaces that do not require magic.
All are newly installed WordPress, with the same template; the article content may differ, but it's negligible. All are txt.
Chrome's built-in lighthouse,
Mode, testing device desktop device,
Proxy turned off, direct access. Testing.
1.xlphp#
During the testing process, I found that CF R2 image hosting cannot upload images directly, so I switched Clash to rule mode. The difference in the second test was not significant; the following all used the same testing environment.
2.alchosting#
acevs.alchosting.xyz/?i=2
Let's look directly at the scores, with a screenshot zoomed in.
Then I logged into the backend; the passwords for WP and the control panel are different. Luckily, I made a password note. The password manager only records the passwords and accounts for the primary domain if no password is set for the subdomain.
3.wuaze#
This space has many free subdomains,
This one sounds like pinyin 无阿泽，so I chose this subdomain.
acevs.wuaze.com/?i=1
4.my-place#
The speeds are all similar
acevs.my-place.us/?i=1
5.beget.tech#
This was the first one I registered. Seems to be Russian.
It passed.
acevs
Hugo GitHub Stack Theme Subsite Testing#
Main Site Testing#
ACEVS – What have you persevered through?
Conclusion: The free ones are actually quite good, haha. Now let's see about durability. Hehe.