Skip to content

The size of styles.css is about 11 MB after uglifying. #991

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
srinivascodes opened this issue Jul 5, 2016 · 7 comments
Closed

The size of styles.css is about 11 MB after uglifying. #991

srinivascodes opened this issue Jul 5, 2016 · 7 comments

Comments

@srinivascodes
Copy link

srinivascodes commented Jul 5, 2016

After running swagger editor on my server, I found that styles.css is almost 11MB and taking long time to get load. After uglifying still the size is 11 MB. Is there any way to optimize it. Also is there any way to load styles.css quickly in the browser.

@saharj
Copy link
Contributor

saharj commented Jul 5, 2016

You're right. It's because we‘re embedding fonts in the CSS file. We will consider improving it later.

@brylie
Copy link

brylie commented Sep 19, 2016

This wait time has a negative effect on end users, in terms of delay to render the page. In our case, the delay is over ten seconds:

screenshot

@brylie
Copy link

brylie commented Sep 19, 2016

Please consider removing these fonts from the CSS file.

@saharj
Copy link
Contributor

saharj commented Sep 20, 2016

@brylie we know it's important but there is a bug in webpack file loader still open. That issue needs to be fixed before we take any action toward fixing this issue.

@leotu
Copy link

leotu commented Jan 23, 2017

+1, it take me 1.7 minutes :-(

css-too-large

@webron
Copy link
Contributor

webron commented Jun 8, 2017

Apologies for the delayed feedback.

Unfortunately, our code base might have deviated from the time this PR was submitted, and we cannot easily merge it (certainly not against master), and so, we're going to close this PR.

If you find the change important and would like to resubmit it, please let us know. Be aware that we are focused on the 3.X version at the moment (now master), and new changes should be applied to it.

We appreciate the time you've taken into submitting this PR. We're now making extra effort to review PRs within a few days at most, to avoid situations like this.

@webron webron closed this as completed Jun 8, 2017
@webron
Copy link
Contributor

webron commented Jun 8, 2017

Huh, I meant to post it on the relevant PR. However, this should no longer be an issue in 3.X.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants