Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

dynpage.net

DynPage - A simple Content Management System based on CKeditor

Page Load Speed

2 sec in total

First Response

363 ms

Resources Loaded

1.4 sec

Page Rendered

228 ms

dynpage.net screenshot

About Website

Click here to check amazing Dyn Page content. Otherwise, check out these important facts you probably never knew about dynpage.net

DynPage allows you to edit Websites online and make content editable with an HTML editor.

Visit dynpage.net

Key Findings

We analyzed Dynpage.net page load time and found that the first response time was 363 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

dynpage.net performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

dynpage.net

363 ms

style.css

97 ms

jquery.min.js

517 ms

dynpage_load.js

193 ms

logo_dynpage.png

98 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that all of those requests were addressed to Dynpage.net and no external sources were called. The less responsive or slowest element that took the longest time to load (517 ms) belongs to the original domain Dynpage.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.5 kB (38%)

Content Size

139.2 kB

After Optimization

86.7 kB

In fact, the total size of Dynpage.net main page is 139.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. Images take 75.3 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 3.0 kB

  • Original 5.0 kB
  • After minification 4.9 kB
  • After compression 2.0 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 3.0 kB or 60% of the original size.

Image Optimization

-14%

Potential reduce by 10.5 kB

  • Original 75.3 kB
  • After minification 64.8 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, Dyn Page needs image optimization as it can save up to 10.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 37.2 kB

  • Original 56.4 kB
  • After minification 55.6 kB
  • After compression 19.2 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 37.2 kB or 66% of the original size.

CSS Optimization

-72%

Potential reduce by 1.8 kB

  • Original 2.4 kB
  • After minification 1.8 kB
  • After compression 673 B

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. Dynpage.net needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 72% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dyn Page. According to our analytics all requests are already optimized.

Accessibility Review

dynpage.net accessibility score

81

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.

Internationalization and localization

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

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Links do not have a discernible name

Best Practices

dynpage.net best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dynpage.net SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dynpage.net 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 Dynpage.net 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 description is not detected on the main page of Dyn Page. 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: