135editor.com website review

15 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.

A phone's processor spends 6.1 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

131 files are served with short cache lifetimes, so returning visitors download them again (8.7 MB).

23 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.

7 long tasks block the main thread while loading, the longest for 478 ms. During a long task the page ignores taps.

About 77 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

About 33 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

23 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying CSS.

1 third-party service load with your homepage (idqqimg.com), adding 2 KiB and 0 ms of main-thread time.

Visually, the page fills in at 21.3 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 9.1 s. Good is under 3.8 s.

Scripts block taps and scrolling for 529 ms in total while the page loads. Good is under 200 ms.

The first text or image appears after 2.1 s on a phone. Good is under 1.8 s.

16 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 8.8 MB in 158 requests on a phone: images 8.5 MB (130), scripts 188 KiB (12) and stylesheets 76 KiB (11). Under 2 MB keeps phones on slow connections fast.

2 images (110 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 2.49 g of CO₂e: 298.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

7 images have no alt text, which hurts accessibility and image search.

5 elements use ARIA attributes their role does not allow, which confuses screen readers.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 116 pages on 135editor.com and 38 external pages.

There is no https://www.135editor.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.135editor.com/bindex.html declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.135editor.com/bindex.html all use the title “135编辑器 - 专业公众号排版工具_微信公众号编辑器_智能AI排版”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.135editor.com/bige_pic has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.135editor.com/yangshi.html and https://www.135editor.com/svg-center.html use the same meta description. A description written for each page earns more clicks.

https://www.135editor.com/beautify_editor.html, https://www.135editor.com/moban.html, https://www.135editor.com/yangshi.html, https://www.135editor.com/bige_pic, https://www.135editor.com/svg-center.html and https://www.135editor.com/svgeditor/svgAttract.html and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.135editor.com/bindex.html, https://www.135editor.com/moban.html, https://www.135editor.com/yangshi.html, https://www.135editor.com/bige_pic, https://www.135editor.com/svg-center.html and https://www.135editor.com/schedules/calendar/f718cebb39233bcebfa70df6d26c1667 and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.135editor.com/bindex.html, https://www.135editor.com/beautify_editor.html, https://www.135editor.com/moban.html, https://www.135editor.com/yangshi.html, https://www.135editor.com/bige_pic and https://www.135editor.com/svgeditor/svgAttract.html and 1 other took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 57 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://www.135editor.com/.

3 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 41 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 2 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.