Platohagel: I want to know why the WordPress Cimo plugin did not succeed in your Data Compression Rate value?
Yes. I think the discrepancy is important, because Cimo did not necessarily “fail” in the ordinary sense; it was optimizing toward a different objective than the compression method I used on your video.
I checked Cimo’s current documentation, and there are several reasons.
1. Cimo’s video compression is not the same process I used
Cimo Premium can optimize video and can downscale resolution, but its stated purpose is general media optimization rather than targeting a particular very-low file size.
For the video you gave me:
Original: 193.7 MB
Our compressed version: 13.5 MB
That is approximately:
93% reduction
or, put another way, the resulting file is only about 7% of the original size.
That is a very aggressive compression target.
⸻
2. Cimo’s philosophy is deliberately conservative
Cimo’s current Bulk Optimization documentation says its Smart Optimization makes repeated passes until it detects a slight noticeable degradation in quality.
That is fundamentally different from the approach we used.
I approached your video from the perspective:
What is the smallest practical WordPress video we can make while retaining the complete song, acceptable visual quality, and 16:9 presentation?
Cimo approaches it more like:
How much can we reduce this while maintaining essentially the original visual experience?
Those are different optimization goals.
⸻
3. The enormous reduction comes principally from video bitrate
This is the key point.
A video file is not large merely because it is 5 minutes long. Its size is heavily determined by:
resolution + frame rate + codec + video bitrate + audio bitrate
Our compression reduced the amount of data devoted to each second of video substantially.
Cimo can also resize video to a lower resolution, according to its documentation. But it isn’t documented as providing the same sort of explicit target-file-size strategy that we used.
So Cimo may decide:
“This video is still visually good at a relatively high bitrate.”
whereas our process asks:
“Can this video be represented adequately using substantially fewer bits per second?”
That difference can be enormous.
⸻
4. There is another important Cimo issue:
backup files
This could be especially important for your Eskesthai storage problem.
Cimo’s Bulk Optimization automatically keeps the original as a backup. The documentation says the backup uses a -backup suffix and can subsequently be deleted to recover the storage.
Therefore, suppose Cimo changed:
193.7 MB → 80 MB
You might think you saved 113.7 MB.
But if Cimo retains:
- original = 193.7 MB
- optimized = 80 MB
- backup = another copy of original
then your Media Library could temporarily contain considerably more storage, not less.
Cimo explicitly provides a Delete Backup function for this reason.
For your particular objective—reducing Eskesthai’s WordPress storage consumption—this matters greatly.
⸻
The more interesting discovery
I think we have now identified something useful for the Eskesthai Legacy Operating Manual:
╔══════════════════════════════════════════════════════════╗
CIMO → QUALITY-FIRST OPTIMIZATION
OUR METHOD → STORAGE-FIRST OPTIMIZATION
ESKESTHAI → BALANCED LEGACY OPTIMIZATION
╚══════════════════════════════════════════════════════════╝
We don’t necessarily want the smallest possible video.
We want the smallest file that still preserves the artistic work.
For your music videos, that gives us a much better standard:
Original master
↓
Compressed archival/web version
↓
Verify duration
↓
Verify audio
↓
Verify visual quality
↓
Delete unnecessary duplicate/backup
↓
Keep only the version actually required by WordPress
And there is one particularly useful thing we can do next:
Take the exact same video and compare the Cimo-produced version against our 13.5 MB version.
If you still have the Cimo-compressed copy, upload it here. I can measure both files objectively—MB, bitrate, resolution, frame rate, audio bitrate and duration—and we can discover exactly where Cimo stopped compressing and why.
Platohagel:
Details
Uploaded on: October 5, 2026
Uploaded by: [PlatoHagel]
Uploaded to: [Cross-Mode Modalities Compressed]
File name: Cross-mode-Modalities-.mov
File type: video/quicktime
File size: 409 MB
Socrates:
Yes. 409 MB is the important clue. If Cimo produced or accepted Cross-mode-Modalities-.mov as the supposedly optimized file, then it did not achieve the kind of compression we are trying to achieve for Eskesthai.
There is an important distinction, however.
What Cimo says it should do
Cimo Premium says it can:
- compress video,
- convert video to MP4,
- resize video to lower resolutions,
- and apply its video settings during bulk optimization.
But Cimo also says that its Bulk Optimization preserves the original video format. Thus, a MOV remains MOV rather than automatically becoming MP4 during bulk processing.
That may be exactly what we are seeing here.
Your 409 MB file
The record says:
Cross-mode-Modalities-.mov
409 MB
That is a QuickTime MOV, not an MP4.
For our Eskesthai compression program, that is already a warning sign.
The compression method I used on From Hidden Flow to Living Light produced:
193.7 MB → 13.5 MB
while retaining the complete 5:05 soundtrack.
That is the type of transformation we are looking for.
Why Cimo may have left this one at 409 MB
There are three likely possibilities:
1. It was processed through Cimo’s bulk optimizer.
Cimo specifically says unsupported formats can be skipped, and that only browser-compatible formats appear in its bulk optimizer.
2. MOV compatibility prevented the intended video conversion.
Cimo’s documentation says that its Premium upload optimization can convert videos to MP4, but its bulk optimizer preserves formats.
3. Cimo’s optimization target is not the same as ours.
Cimo’s Smart Optimization repeatedly reduces quality until it detects a slight noticeable degradation. It is therefore looking for a quality/size balance rather than a specific aggressive storage target.
⸻
I think we have discovered something important for the Eskesthai project
We should not regard “Cimo optimized” as equivalent to “properly compressed for the Eskesthai archive.”
Instead:
╔════════════════════════════════════════════════════════════╗
ORIGINAL VIDEO
↓
CIMO — preliminary optimization
↓
INSPECT FORMAT / RESOLUTION / BITRATE / SIZE
↓
OUR ESKESTHAI COMPRESSION STANDARD
↓
H.264 MP4 + AAC
↓
QUALITY CHECK
↓
WORDPRESS VERSION
╚════════════════════════════════════════════════════════════╝
And 409 MB is not acceptable as the final web copy if the same visual/audio material can be represented substantially smaller.
One thing I would
not
do yet
I would not delete the 409 MB MOV.
It may be the only existing copy of the video, and it may be your higher-quality source. We should first create a properly compressed MP4 from it and compare the two.
If you upload Cross-mode-Modalities-.mov itself here, rather than only the WordPress details, I can perform the same compression test and give you:
409 MB → ? MB
while preserving the complete soundtrack and duration.
That will give us a direct, measurable answer to whether Cimo has actually failed this particular video or whether the 409 MB file is simply the preserved source/backup.