Tools & Wizards About Us
standardsmap.org screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

standardsmap.org

StandardsMap

Page Load Speed

2.2 sec in total

First Response

288 ms

Resources Loaded

1.7 sec

Page Rendered

248 ms

standardsmap.org screenshot

About Website

Visit standardsmap.org now to see the best up-to-date Standards Map content for Turkey and also check out these interesting facts you probably never knew about standardsmap.org

Visit standardsmap.org

Key Findings

We analyzed Standardsmap.org page load time and found that the first response time was 288 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster. This domain responded with an error, which can significantly jeopardize Standardsmap.org rating and web reputation

Performance Metrics

standardsmap.org performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value1,440 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

standardsmap.org

288 ms

bootstrap.css

179 ms

mainV2.css

276 ms

modernizr-2.6.2.min.js

144 ms

jquery-1.10.1.min.js

239 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 46% of them (29 requests) were addressed to the original Standardsmap.org, 11% (7 requests) were made to Youtube.com and 6% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (508 ms) relates to the external source Syndication.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (69%)

Content Size

1.6 MB

After Optimization

499.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Standardsmap.org main page is 1.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. 65% of websites need less resources to load. CSS take 709.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 45.0 kB

  • Original 54.5 kB
  • After minification 51.1 kB
  • After compression 9.6 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 45.0 kB or 82% of the original size.

Image Optimization

-17%

Potential reduce by 36.7 kB

  • Original 222.1 kB
  • After minification 185.4 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, Standards Map needs image optimization as it can save up to 36.7 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 410.8 kB

  • Original 617.5 kB
  • After minification 607.5 kB
  • After compression 206.7 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 410.8 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 612.0 kB

  • Original 709.7 kB
  • After minification 603.9 kB
  • After compression 97.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. Standardsmap.org needs all CSS files to be minified and compressed as it can save up to 612.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (45%)

Requests Now

56

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

standardsmap.org

standardsmap.org

288 ms

bootstrap.css

bootstrap.css

179 ms

mainV2.css

mainV2.css

276 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

144 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

239 ms

bootstrap.min.js

bootstrap.min.js

189 ms

ekko-lightbox.js

ekko-lightbox.js

105 ms

bootstrap-checkbox.js

bootstrap-checkbox.js

133 ms

frontend-init.js

frontend-init.js

191 ms

buttons.js

buttons.js

6 ms

video.js

video.js

152 ms

vjs.youtube.js

vjs.youtube.js

129 ms

ga.js

ga.js

41 ms

sm-branding.png

sm-branding.png

95 ms

itc-logo.png

itc-logo.png

96 ms

standards-map-heading.png

standards-map-heading.png

30 ms

partner_CBI.png

partner_CBI.png

31 ms

partner_SHDB.png

partner_SHDB.png

92 ms

Lecture%201.jpg

Lecture%201.jpg

94 ms

Lecture%202.jpg

Lecture%202.jpg

96 ms

Lecture%203.png

Lecture%203.png

98 ms

Lecture%204.png

Lecture%204.png

96 ms

Lecture5.jpg

Lecture5.jpg

160 ms

IDENTIFY_Vid.jpg

IDENTIFY_Vid.jpg

96 ms

QUICK3_Vid.jpg

QUICK3_Vid.jpg

97 ms

COMPARE3_Vid.jpg

COMPARE3_Vid.jpg

98 ms

SA3_Vid.jpg

SA3_Vid.jpg

159 ms

logo-footer-1.png

logo-footer-1.png

160 ms

logo-footer-2.png

logo-footer-2.png

161 ms

widgets.js

widgets.js

71 ms

Login.aspx

Login.aspx

359 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

133 ms

getAllAppDefault.esi

getAllAppDefault.esi

283 ms

iframe_api

iframe_api

115 ms

inpage_linkid.js

inpage_linkid.js

64 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

67 ms

hRghHKufMW8

hRghHKufMW8

114 ms

KJpk7qdf0D4

KJpk7qdf0D4

85 ms

x-wIAU2940A

x-wIAU2940A

118 ms

homepage_carousel_images_1.png

homepage_carousel_images_1.png

44 ms

5PLB6HJNau0

5PLB6HJNau0

136 ms

hRghHKufMW8

hRghHKufMW8

100 ms

__utm.gif

__utm.gif

28 ms

www-widgetapi.js

www-widgetapi.js

64 ms

HSbFLwC6VSs

HSbFLwC6VSs

178 ms

syndication

syndication

508 ms

469250848791351296

469250848791351296

507 ms

collect

collect

493 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

52 ms

www-embed-player.js

www-embed-player.js

79 ms

base.js

base.js

146 ms

getSegment.php

getSegment.php

362 ms

checkOAuth.esi

checkOAuth.esi

364 ms

Login.aspx

Login.aspx

364 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

229 ms

ad_status.js

ad_status.js

254 ms

t.dhj

t.dhj

357 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

102 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

103 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

17 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

18 ms

36570_374838425886602_343634492340329_942443_1563713655_n_normal.jpg

36570_374838425886602_343634492340329_942443_1563713655_n_normal.jpg

167 ms

Cdf-cv9WwAAoKWK.jpg:small

Cdf-cv9WwAAoKWK.jpg:small

56 ms

Accessibility Review

standardsmap.org accessibility score

92

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

standardsmap.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

standardsmap.org SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Standardsmap.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 Standardsmap.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.

Social Sharing Optimization

standardsmap.org

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