5.1 sec in total
27 ms
4.4 sec
670 ms
Welcome to textbox.io homepage info - get ready to check Text Box best content for India right away, or after learning these important things about textbox.io
TinyMCE is the most advanced WYSIWYG HTML editor designed to simplify website content creation. The rich text editing platform that helped launched Atlassian, Medium, Evernote and more.
Visit textbox.ioWe analyzed Textbox.io page load time and found that the first response time was 27 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
textbox.io performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value10.3 s
0/100
25%
Value6.6 s
38/100
10%
Value390 ms
68/100
30%
Value0.082
94/100
15%
Value9.1 s
33/100
10%
27 ms
2208 ms
80 ms
165 ms
179 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 12% of them (6 requests) were addressed to the original Textbox.io, 24% (12 requests) were made to 1p299h3n07ros00d71qu1tug-wpengine.netdna-ssl.com and 10% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Textbox.io.
Page size can be reduced by 1.3 MB (69%)
1.9 MB
582.0 kB
In fact, the total size of Textbox.io main page is 1.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. CSS take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 67.3 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 67.3 kB or 84% of the original size.
Potential reduce by 7.1 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Text Box images are well optimized though.
Potential reduce by 352.2 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 352.2 kB or 67% of the original size.
Potential reduce by 858.7 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Textbox.io needs all CSS files to be minified and compressed as it can save up to 858.7 kB or 85% of the original size.
Number of requests can be reduced by 20 (50%)
40
20
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Text Box. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
textbox.io
27 ms
textbox.io
2208 ms
autoptimize_159b256427a7e8dc0462f213e2ba7f80.css
80 ms
css
165 ms
css
179 ms
getEditor
466 ms
run_prettify.js
75 ms
conversion.js
142 ms
autoptimize_336f93b6f8e05fc8c5d0a14eeca30ff9.js
143 ms
analytics.js
46 ms
linkid.js
10 ms
collect
12 ms
collect
52 ms
ga-audiences
40 ms
textboxio.css
56 ms
prettify.css
21 ms
color-ondark@2x.png
16 ms
textbox.jpg
94 ms
asp-300x110.png
13 ms
knockout-300x73.png
13 ms
xpages-300x88.png
90 ms
angularjs-1-300x77.png
90 ms
LotusWebContentManagementICON.png
92 ms
unnamed.png
93 ms
rss.png
93 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
417 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
444 ms
vzIUHo9z-oJ4WgkpPOtg1_esZW2xOQ-xsNqO47m55DA.woff
470 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
588 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
587 ms
fontawesome-webfont.woff
386 ms
mdfonticon.woff
416 ms
loader0.js
585 ms
sky.jpg
211 ms
tbio-ipad-big-opt.png
85 ms
autocorrect
360 ms
codemirror.css
56 ms
2151-351-10-2762.js
248 ms
pd.js
274 ms
wordimport.js
167 ms
correction
249 ms
autocorrect
77 ms
content.css
59 ms
typebase.css
60 ms
c
222 ms
application2.js
110 ms
IELgSIBTYFfAXSBgoGQAZgBoAGuAbsB2AHwgfmCDYIdAiQCRQJjAnuClwKqAr4C3ALjAugDAIMHgxUDGgMfAyQDKQMsgzADNYM8A0SDTgNdA2iDb4N5g5KDoQOnA8EDyIPYA+WD64QCBBSEH4QqBDSEQARVhF4EaIRzBHsEg4SMBJSEnwSphLMEvwTIBNIFAoUShSIFMYVEBXYFeYWDBY4FoQWygAAAAEAAABmAKEACgAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAOAK4AAQAAAAAAAQAMAAAAAQAAAAAAAgAHAI0AAQAAAAAAAwAMAEUAAQAAAAAABAAMAKIAAQAAAAAABQALACQAAQAAAAAABgAMAGkAAQAAAAAACgAaAMYAAwABBAkAAQAYAAwAAwABBAkAAgAOAJQAAwABBAkAAwAYAFEAAwABBAkABAAYAK4AAwABBAkABQAWAC8AAwABBAkABgAYAHUAAwABBAkACgA0AOB0ZXh0Ym94SWNvbnMAdABlAHgAdABiAG8AeABJAGMAbwBuAHNWZXJzaW9uIDEuMABWAGUAcgBzAGkAbwBuACAAMQAuADB0ZXh0Ym94SWNvbnMAdABlAHgAdABiAG8AeABJAGMAbwBuAHN0ZXh0Ym94SWNvbnMAdABlAHgAdABiAG8AeABJAGMAbwBuAHNSZWd1bGFyAFIAZQBnAHUAbABhAHJ0ZXh0Ym94SWNvbnMAdABlAHgAdABiAG8AeABJAGMAbwBuAHNGb250IGdlbmVyYXRlZCBieSBJY29Nb29uLgBGAG8AbgB0ACAAZwBlAG4AZQByAGEAdABlAGQAIABiAHkAIABJAGMAbwBNAG8AbwBuAC4AAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
4 ms
analytics
277 ms
correction
72 ms
storage.html
29 ms
storage.js
29 ms
textbox.io accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
textbox.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
textbox.io SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Textbox.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Textbox.io main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
textbox.io
Open Graph description is not detected on the main page of Text Box. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: