2.4 sec in total
234 ms
2.1 sec
140 ms
Click here to check amazing Floridastandards content. Otherwise, check out these important facts you probably never knew about floridastandards.org
>
Visit floridastandards.orgWe analyzed Floridastandards.org page load time and found that the first response time was 234 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
floridastandards.org performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value3.7 s
58/100
25%
Value3.5 s
88/100
10%
Value170 ms
92/100
30%
Value0.099
90/100
15%
Value4.2 s
86/100
10%
234 ms
45 ms
66 ms
68 ms
24 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Floridastandards.org, 5% (3 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (424 ms) relates to the external source Sts.fldoesso.org.
Page size can be reduced by 2.7 MB (76%)
3.6 MB
843.1 kB
In fact, the total size of Floridastandards.org main page is 3.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 41.8 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. This page needs HTML code to be minified as it can gain 8.9 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 41.8 kB or 80% of the original size.
Potential reduce by 973.0 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. Obviously, Floridastandards needs image optimization as it can save up to 973.0 kB or 78% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.3 MB
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 1.3 MB or 72% of the original size.
Potential reduce by 426.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. Floridastandards.org needs all CSS files to be minified and compressed as it can save up to 426.7 kB or 87% of the original size.
Number of requests can be reduced by 23 (46%)
50
27
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floridastandards. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.cpalms.org
234 ms
index.aspx
45 ms
66 ms
bootstrap.css
68 ms
bootstrap-combobox.css
24 ms
font-awesome.css
7 ms
main.css
16 ms
Aim.css
10 ms
kendo.default.min.css
8 ms
kendo.common.min.css
23 ms
jquery-1.11.3.min.js
18 ms
modernizr-2.5.3.js
20 ms
jwplayer.js
19 ms
jquery.address.js
36 ms
jquery.validate.js
63 ms
bootstrap.js
33 ms
bootbox.js
28 ms
bootstrap-typeahead.js
27 ms
bootstrap-combobox.js
63 ms
jquery.form.js
32 ms
jquery.keyfilter.js
39 ms
main.js
61 ms
kendo.all.min.js
57 ms
kendo.aspnetmvc.min.js
60 ms
Aim.js
288 ms
css
16 ms
424 ms
jwpsrv.js
183 ms
cpalms_color.png
91 ms
sso-icon.png
19 ms
floridastudents.jpg
91 ms
sunny_logo.png
32 ms
VideoPreview.png
92 ms
mfas_icon.png
38 ms
lesson_plan_dev_icon.png
39 ms
students_icon.png
40 ms
MEA_icon.png
92 ms
beyondstandards_icon.png
93 ms
perspective_icon.png
90 ms
content_complex_icon.png
95 ms
lesson_study_icon.png
97 ms
ccss_standards_icon.png
93 ms
resources_icon.png
95 ms
review_process_icon.png
101 ms
planner_icon.jpg
98 ms
lsss_icon.jpg
93 ms
visualizer_icon.jpg
96 ms
myresources_icon.jpg
95 ms
facebook.jpg
99 ms
twitter.png
96 ms
cpalms_white.png
104 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
13 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
24 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
25 ms
fontawesome-webfont.woff
14 ms
ga.js
16 ms
__utm.gif
28 ms
__utm.gif
9 ms
floridastandards.org accessibility score
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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
floridastandards.org 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
Page has valid source maps
floridastandards.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floridastandards.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Floridastandards.org 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.
floridastandards.org
Open Graph description is not detected on the main page of Floridastandards. 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: