Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 42

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

magglance.com

Mag Glance - create magazine online all by yourself and free of charge

Page Load Speed

4.8 sec in total

First Response

323 ms

Resources Loaded

4.3 sec

Page Rendered

171 ms

magglance.com screenshot

About Website

Visit magglance.com now to see the best up-to-date Mag Glance content for Germany and also check out these interesting facts you probably never knew about magglance.com

Design your own online magazine. Distribute it via a link or ask for a low-cost hardcopy. Printing from 1 copy or more!

Visit magglance.com

Key Findings

We analyzed Magglance.com page load time and found that the first response time was 323 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

magglance.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value390 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.153

75/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

Network Requests Diagram

magglance.com

323 ms

www.magglance.com

519 ms

owl.carousel.css

98 ms

owl.theme.css

195 ms

style-timeline.css

291 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 70% of them (55 requests) were addressed to the original Magglance.com, 30% (24 requests) were made to Prod-img1.magglance.com. The less responsive or slowest element that took the longest time to load (906 ms) belongs to the original domain Magglance.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 85.4 kB (8%)

Content Size

1.1 MB

After Optimization

984.3 kB

In fact, the total size of Magglance.com main page is 1.1 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. 45% of websites need less resources to load. Images take 745.6 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 76.5 kB

  • Original 86.6 kB
  • After minification 70.1 kB
  • After compression 10.1 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 16.5 kB, which is 19% 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 76.5 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 5.7 kB

  • Original 745.6 kB
  • After minification 739.9 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. Mag Glance images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.7 kB

  • Original 218.4 kB
  • After minification 218.4 kB
  • After compression 215.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 512 B

  • Original 19.2 kB
  • After minification 19.2 kB
  • After compression 18.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. Magglance.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 29 (38%)

Requests Now

77

After Optimization

48

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

Accessibility Review

magglance.com accessibility score

67

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

magglance.com best practices score

42

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

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

Browser errors were logged to the console

SEO Factors

magglance.com SEO score

64

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Magglance.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 Magglance.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

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