Tools & Wizards About Us
storymaps-classicqa.arcgis.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

storymaps-classicqa.arcgis.com

Esri Story Maps Retirement | Transition to ArcGIS StoryMaps

Page Load Speed

1.1 sec in total

First Response

14 ms

Resources Loaded

642 ms

Page Rendered

493 ms

storymaps-classicqa.arcgis.com screenshot

About Website

Welcome to storymaps-classicqa.arcgis.com homepage info - get ready to check Story Maps Classicqa ArcGIS best content for United States right away, or after learning these important things about storymaps-classicqa.arcgis.com

Learn how to transition from classic Esri Story Maps to ArcGIS StoryMaps. Compare features and access resources to continue sharing stories with maps.

Visit storymaps-classicqa.arcgis.com

Key Findings

We analyzed Storymaps-classicqa.arcgis.com page load time and found that the first response time was 14 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

storymaps-classicqa.arcgis.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.9 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value3,490 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.155

74/100

15%

TTI (Time to Interactive)

Value22.3 s

1/100

10%

Network Requests Diagram

storymaps-classicqa.arcgis.com

14 ms

storymaps-classicqa.arcgis.com

13 ms

classic-storymaps-home

157 ms

classic

41 ms

rum-standalone.js

55 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Storymaps-classicqa.arcgis.com, 68% (30 requests) were made to Esri.com and 14% (6 requests) were made to Webapps-cdn.esri.com. The less responsive or slowest element that took the longest time to load (388 ms) relates to the external source Esri.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (44%)

Content Size

2.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Storymaps-classicqa.arcgis.com main page is 2.4 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. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 57.3 kB

  • Original 75.2 kB
  • After minification 66.9 kB
  • After compression 17.9 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.3 kB, which is 11% 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 57.3 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 950.5 kB
  • After minification 950.5 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. Story Maps Classicqa ArcGIS images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 934.7 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 338.6 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 934.7 kB or 73% of the original size.

CSS Optimization

-58%

Potential reduce by 52.5 kB

  • Original 91.0 kB
  • After minification 90.7 kB
  • After compression 38.5 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. Storymaps-classicqa.arcgis.com needs all CSS files to be minified and compressed as it can save up to 52.5 kB or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (69%)

Requests Now

39

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

storymaps-classicqa.arcgis.com

storymaps-classicqa.arcgis.com

14 ms

storymaps-classicqa.arcgis.com

storymaps-classicqa.arcgis.com

13 ms

classic-storymaps-home

classic-storymaps-home

157 ms

classic

classic

41 ms

rum-standalone.js

rum-standalone.js

55 ms

calcite.css

calcite.css

66 ms

esriChat.css

esriChat.css

63 ms

geoip.js

geoip.js

70 ms

datalayer.js

datalayer.js

40 ms

components.css

components.css

58 ms

launch-EN26af1ee4ef084984926fd80d1cb93835.min.js

launch-EN26af1ee4ef084984926fd80d1cb93835.min.js

94 ms

gn.css

gn.css

91 ms

gn.js

gn.js

99 ms

clientlibs.css

clientlibs.css

52 ms

clientlibs.css

clientlibs.css

99 ms

clientlibs.js

clientlibs.js

99 ms

clientlibs.css

clientlibs.css

111 ms

clientlibs.js

clientlibs.js

257 ms

clientlibs.css

clientlibs.css

123 ms

clientlibs.css

clientlibs.css

110 ms

clientlibs.css

clientlibs.css

240 ms

clientlibs.css

clientlibs.css

118 ms

clientlibs.js

clientlibs.js

185 ms

clientlibs.js

clientlibs.js

162 ms

clientlibs.css

clientlibs.css

221 ms

clientlibs.css

clientlibs.css

388 ms

csrf.js

csrf.js

169 ms

container.js

container.js

185 ms

components.js

components.js

201 ms

esriChat.js

esriChat.js

87 ms

instantpage.min.js

instantpage.min.js

65 ms

rum-standalone.js

rum-standalone.js

88 ms

clientlib-dependencies.js

clientlib-dependencies.js

254 ms

fonts.css

fonts.css

4 ms

subpage-banner-product-roadmap.png

subpage-banner-product-roadmap.png

127 ms

2025-storymap-roadmap.jpg

2025-storymap-roadmap.jpg

159 ms

2023-storymap-roadmap.jpg

2023-storymap-roadmap.jpg

182 ms

2021-storymap-roadmap.jpg

2021-storymap-roadmap.jpg

195 ms

2019-storymap-roadmap.jpg

2019-storymap-roadmap.jpg

181 ms

2011-storymap-roadmap.jpg

2011-storymap-roadmap.jpg

303 ms

moving-to-arcgis-storymaps-card-1.jpg

moving-to-arcgis-storymaps-card-1.jpg

180 ms

mimicking-the-classic-templates-in-arcgis-storymaps-card-2.jpg

mimicking-the-classic-templates-in-arcgis-storymaps-card-2.jpg

229 ms

recreating-classic-story-maps-in-arcgis-storymaps-card-3.jpg

recreating-classic-story-maps-in-arcgis-storymaps-card-3.jpg

211 ms

1.css

1.css

60 ms

Accessibility Review

storymaps-classicqa.arcgis.com accessibility score

92

Accessibility Issues

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

Buttons do not have an accessible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

[lang] attributes do not have a valid value

Best Practices

storymaps-classicqa.arcgis.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

storymaps-classicqa.arcgis.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

storymaps-classicqa.arcgis.com

Open Graph data is detected on the main page of Story Maps Classicqa ArcGIS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: