Tools & Wizards About Us
api.dojotoolkit.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

api.dojotoolkit.org

API Documentation - The Dojo Toolkit Version 1.10

Page Load Speed

1.9 sec in total

First Response

183 ms

Resources Loaded

1.6 sec

Page Rendered

105 ms

api.dojotoolkit.org screenshot

About Website

Welcome to api.dojotoolkit.org homepage info - get ready to check API Dojo Toolkit best content for India right away, or after learning these important things about api.dojotoolkit.org

Dojo toolkit API documentation viewer, version 1.10

Visit api.dojotoolkit.org

Key Findings

We analyzed Api.dojotoolkit.org page load time and found that the first response time was 183 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

api.dojotoolkit.org performance score

0

Network Requests Diagram

api.dojotoolkit.org

183 ms

151 ms

index.css

205 ms

api.css

272 ms

dojo.js

450 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Api.dojotoolkit.org, 85% (60 requests) were made to Dojotoolkit.org and 11% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (450 ms) relates to the external source Dojotoolkit.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 506.9 kB (73%)

Content Size

698.7 kB

After Optimization

191.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Api.dojotoolkit.org main page is 698.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 432.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 17.6 kB

  • Original 21.6 kB
  • After minification 20.4 kB
  • After compression 4.0 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 17.6 kB or 81% of the original size.

JavaScript Optimization

-66%

Potential reduce by 287.9 kB

  • Original 432.9 kB
  • After minification 415.3 kB
  • After compression 145.1 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 287.9 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 201.5 kB

  • Original 244.2 kB
  • After minification 243.6 kB
  • After compression 42.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. Api.dojotoolkit.org needs all CSS files to be minified and compressed as it can save up to 201.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (93%)

Requests Now

60

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of API Dojo Toolkit. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

api.dojotoolkit.org

api.dojotoolkit.org

183 ms

151 ms

index.css

index.css

205 ms

api.css

api.css

272 ms

dojo.js

dojo.js

450 ms

api.js

api.js

142 ms

shCore.js

shCore.js

213 ms

shBrushJScript.js

shBrushJScript.js

144 ms

shBrushXml.js

shBrushXml.js

213 ms

css

css

26 ms

font-awesome.min.css

font-awesome.min.css

17 ms

dojo_en-us.js

dojo_en-us.js

67 ms

BorderContainer.js

BorderContainer.js

72 ms

TabContainer.js

TabContainer.js

73 ms

ModuleContentPane.js

ModuleContentPane.js

73 ms

AccordionContainer.js

AccordionContainer.js

75 ms

ModuleTreeModel.js

ModuleTreeModel.js

75 ms

ModuleTree.js

ModuleTree.js

129 ms

MenuItem.js

MenuItem.js

132 ms

Menu.js

Menu.js

134 ms

MenuSeparator.js

MenuSeparator.js

135 ms

FilteringSelect.js

FilteringSelect.js

136 ms

RFda8w1V0eDZheqfcyQ4EInF5uFdDttMLvmWuJdhhgs.ttf

RFda8w1V0eDZheqfcyQ4EInF5uFdDttMLvmWuJdhhgs.ttf

26 ms

ZvcMqxEwPfh2qDWBPxn6ngV_pQ1T3xN3K1c3sB361us.ttf

ZvcMqxEwPfh2qDWBPxn6ngV_pQ1T3xN3K1c3sB361us.ttf

63 ms

ZvcMqxEwPfh2qDWBPxn6nn06qf9KHRHwsVx7iw5MXmY.ttf

ZvcMqxEwPfh2qDWBPxn6nn06qf9KHRHwsVx7iw5MXmY.ttf

63 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

63 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

63 ms

zJY4gsxBiSo5L7tNutxFNg.ttf

zJY4gsxBiSo5L7tNutxFNg.ttf

72 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

63 ms

icomoon_icons.woff

icomoon_icons.woff

164 ms

icomoon_icons.ttf

icomoon_icons.ttf

221 ms

ViZhet7Ak-LRXZMXzuAfkZ0EAVxt0G0biEntp43Qt6E.ttf

ViZhet7Ak-LRXZMXzuAfkZ0EAVxt0G0biEntp43Qt6E.ttf

61 ms

LayoutContainer.js

LayoutContainer.js

116 ms

_TabContainerBase.js

_TabContainerBase.js

106 ms

TabController.js

TabController.js

109 ms

ScrollingTabController.js

ScrollingTabController.js

110 ms

CheckBox.js

CheckBox.js

168 ms

StackContainer.js

StackContainer.js

177 ms

blank.gif

blank.gif

174 ms

Tree.js

Tree.js

146 ms

_Contained.js

_Contained.js

142 ms

DropDownMenu.js

DropDownMenu.js

194 ms

MappedTextBox.js

MappedTextBox.js

193 ms

ComboBoxMixin.js

ComboBoxMixin.js

201 ms

_LayoutWidget.js

_LayoutWidget.js

135 ms

StackController.js

StackController.js

137 ms

_WidgetsInTemplateMixin.js

_WidgetsInTemplateMixin.js

134 ms

ToggleButton.js

ToggleButton.js

122 ms

_CheckBoxMixin.js

_CheckBoxMixin.js

127 ms

_KeyNavMixin.js

_KeyNavMixin.js

123 ms

TreeStoreModel.js

TreeStoreModel.js

123 ms

ForestStoreModel.js

ForestStoreModel.js

135 ms

_dndSelector.js

_dndSelector.js

136 ms

_MenuBase.js

_MenuBase.js

132 ms

ValidationTextBox.js

ValidationTextBox.js

132 ms

QueryResults.js

QueryResults.js

126 ms

_AutoCompleterMixin.js

_AutoCompleterMixin.js

128 ms

_ComboBoxMenu.js

_ComboBoxMenu.js

138 ms

_ToggleButtonMixin.js

_ToggleButtonMixin.js

93 ms

_dndContainer.js

_dndContainer.js

110 ms

_KeyNavContainer.js

_KeyNavContainer.js

69 ms

Tooltip.js

Tooltip.js

76 ms

validate.js

validate.js

77 ms

DataList.js

DataList.js

76 ms

_SearchMixin.js

_SearchMixin.js

89 ms

_ComboBoxMenuMixin.js

_ComboBoxMenuMixin.js

112 ms

_ListMouseMixin.js

_ListMouseMixin.js

114 ms

Memory.js

Memory.js

67 ms

ComboBox.js

ComboBox.js

71 ms

_ListBase.js

_ListBase.js

68 ms

SimpleQueryEngine.js

SimpleQueryEngine.js

72 ms

SEO Factors

api.dojotoolkit.org SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Api.dojotoolkit.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Api.dojotoolkit.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

api.dojotoolkit.org

Open Graph description is not detected on the main page of API Dojo Toolkit. 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: