Tools & Wizards About Us
glancermagazine.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

glancermagazine.com

Glancer Magazine | Local News & Events | West Suburban Chicago

Page Load Speed

2.4 sec in total

First Response

275 ms

Resources Loaded

2 sec

Page Rendered

85 ms

glancermagazine.com screenshot

About Website

Welcome to glancermagazine.com homepage info - get ready to check Glancer Magazine best content for United States right away, or after learning these important things about glancermagazine.com

DAILY • WEEKLY • MONTHLY Glancer Magazine is a Digital Lifestyle Magazine Featuring West Suburban Chicago...At a Glance! Covering Local News, Events, Resident Stories & More for Naperville, Wheaton, G...

Visit glancermagazine.com

Key Findings

We analyzed Glancermagazine.com page load time and found that the first response time was 275 ms and then it took 2.1 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.

Performance Metrics

glancermagazine.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.507

16/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

www.glancermagazine.com

275 ms

bt

73 ms

require.min.js

51 ms

main-r.min.js

61 ms

viewer.css

52 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Glancermagazine.com, 75% (30 requests) were made to Static.parastorage.com and 13% (5 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (446 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (77%)

Content Size

2.9 MB

After Optimization

663.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Glancermagazine.com main page is 2.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. 80% 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 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 60.3 kB

  • Original 75.2 kB
  • After minification 75.0 kB
  • After compression 14.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. 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 60.3 kB or 80% of the original size.

JavaScript Optimization

-77%

Potential reduce by 2.1 MB

  • Original 2.7 MB
  • After minification 2.7 MB
  • After compression 639.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 2.1 MB or 77% of the original size.

CSS Optimization

-84%

Potential reduce by 44.1 kB

  • Original 52.5 kB
  • After minification 49.5 kB
  • After compression 8.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. Glancermagazine.com needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (72%)

Requests Now

39

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.glancermagazine.com

www.glancermagazine.com

275 ms

bt

bt

73 ms

require.min.js

require.min.js

51 ms

main-r.min.js

main-r.min.js

61 ms

viewer.css

viewer.css

52 ms

ugc-viewer

ugc-viewer

36 ms

dynamicmodel

dynamicmodel

444 ms

c1c9e2_25e4bc1ab6d33c20f587582fe3daa311_5487.json.z

c1c9e2_25e4bc1ab6d33c20f587582fe3daa311_5487.json.z

67 ms

c1c9e2_dfe13e80e8dc5703ce158ccaf8441d66_5487.json.z

c1c9e2_dfe13e80e8dc5703ce158ccaf8441d66_5487.json.z

446 ms

bt

bt

120 ms

skins.min.js

skins.min.js

132 ms

components.min.js

components.min.js

111 ms

utils.min.js

utils.min.js

49 ms

core.min.js

core.min.js

119 ms

react-with-addons.min.js

react-with-addons.min.js

110 ms

lodash.min.js

lodash.min.js

30 ms

TweenMax.min.js

TweenMax.min.js

109 ms

layout.min.js

layout.min.js

105 ms

tpa.min.js

tpa.min.js

112 ms

fonts.min.js

fonts.min.js

107 ms

animations.min.js

animations.min.js

107 ms

swfobject.min.js

swfobject.min.js

106 ms

mousetrap.min.js

mousetrap.min.js

106 ms

tweenEngine.min.js

tweenEngine.min.js

107 ms

DrawSVGPlugin.min.js

DrawSVGPlugin.min.js

107 ms

react-dom.min.js

react-dom.min.js

106 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

109 ms

widgets.min.js

widgets.min.js

109 ms

experiment.js

experiment.js

109 ms

render.min.js

render.min.js

111 ms

wixappsCore.min.js

wixappsCore.min.js

110 ms

wixappsClassics.min.js

wixappsClassics.min.js

111 ms

wixappsBuilder.min.js

wixappsBuilder.min.js

107 ms

zepto.min.js

zepto.min.js

106 ms

color.min.js

color.min.js

105 ms

react-dom-server.min.js

react-dom-server.min.js

264 ms

bt

bt

177 ms

latin.css

latin.css

33 ms

dc.js

dc.js

89 ms

bt

bt

78 ms

Accessibility Review

glancermagazine.com accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

glancermagazine.com best practices score

75

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

glancermagazine.com 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

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

glancermagazine.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: